Load balancer counters are reset to 0 if there are load balancer changes
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 32
Description
CloudStack uses haproxy in VR to implement the load balancer feature. If there are any load balancer changes (add/remove VMs, add/remove rules, etc), the haproxy configuration will be regenerated and haproxy service in VR will be reloaded.
We've found an issue that counters are reset to 0 after haproxy reload, which is incorrect because the existing connections are remain alive.
Before haproxy reload:
After haproxy reload:
An issue has been created in haproxy community: https://discourse.haproxy.org/t/stats-are-reset-to-0-after-haproxy-reload/8051
Users who monitor the load balancer connections, please pay attention to it.
##### ISSUE TYPE
* Bug Report
##### COMPONENT NAME
~~~
VR
~~~
##### CLOUDSTACK VERSION
~~~
4.17
4.18
~~~
##### CONFIGURATION
Advanced network
load balancer
##### OS / ENVIRONMENT
##### SUMMARY
##### STEPS TO REPRODUCE
~~~
~~~
##### EXPECTED RESULTS
~~~
~~~
##### ACTUAL RESULTS
~~~
~~~
Contributor guide
Assessment
This issue has not been assessed yet.