Bug 1260842
Summary: | queries to ceilometer are too slow for horizon and ceilometer client | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | August Simonelli <asimonel> |
Component: | openstack-ceilometer | Assignee: | Eoghan Glynn <eglynn> |
Status: | CLOSED NOTABUG | QA Contact: | Yurii Prokulevych <yprokule> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 (Kilo) | CC: | jruzicka, pbrady, yeylon |
Target Milestone: | --- | ||
Target Release: | 8.0 (Liberty) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-08 05:32:05 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
August Simonelli
2015-09-08 03:20:01 UTC
The 60sec failure time made me think this is something else. I bypassed haproxy by going directly to the ip it was balancing with: ceilometer --debug --os-endpoint http://10.0.1.23:8777/ sample-list and it worked. So haproxy.cfg i added a timeout to ceilometer: listen ceilometer timeout server 2m bind 10.0.1.20:8777 bind 10.0.14.20:8777 server overcloud-controller-0 10.0.1.23:8777 check fall 5 inter 2000 rise 2 the default was 1m as set higher in the file by OSP director. When i did this I could get to my samples but it takes a while: ceilometer --debug meter-list real 3m7.002s user 1m0.061s sys 0m3.088s either ceilometer needs to be quicker or haproxy needs to be changed. this also breaks horizon. i'll log another BZ for that. see https://bugzilla.redhat.com/show_bug.cgi?id=1260844 for how this affects horizon by a big query i guess i mean this: [root@overcloud-controller-0 ~ (overcloud-site2)] $ time ceilometer sample-list| wc -l 135519 real 2m54.349s user 0m59.231s sys 0m1.548s changing haproxy does solve this. so i don't see this as a bug but rather a misconfig on my part. closing. |