neutron-lbaas health monitor timeout and delay values interpreted as milliseconds
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Paul Glass | ||
octavia |
Fix Released
|
Medium
|
Paul Glass |
Bug Description
The timeout and delay values on the health monitor objects in Neutron LBaaS are purportedly in units of seconds, but the numeric value is passed all the the way down to the HAProxy configuration[1] file (in both the HAProxy namespace driver and Octavia) where it is interpreted in milliseconds:
* https:/
* https:/
Due to this unit mismatch, a user may configure a pool with a reasonable 10 second timeout, and the service may appear to function normally until even a small load causes the backend servers to exceed a 10 millisecond timeout and then they are removed from the pool.
A timeout value less than one second is useful some settings, such as monitoring a pool of backend servers serving static content, let the database field stores this value as an integer.
description: | updated |
summary: |
- neutron-lbaas health monitor timeout and delay values intepreated as + neutron-lbaas health monitor timeout and delay values interpreted as milliseconds |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in octavia: | |
importance: | Undecided → Medium |
information type: | Public → Public Security |
information type: | Public Security → Public |
Updating template to use value as seconds was discussed in https:/ /review. openstack. org/#/c/ 339260/, but favored updating documentation instead so not to alter behavior of existing deployed load balancers.