Improve failed mysql node removal time in HA deployments
Bug #1639189 reported by
Chris Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Undecided
|
Chris Jones | ||
Bug Description
The current haproxy.pp in puppet-triplo uses most of its global defaults when deploying HA mysql.
These settings (specifically "fall 5" "inter 2000") mean that a failed database node will not be removed from the proxy for 10 seconds. During this time, any OpenStack services which queries the database will return errors, causing confusion and delay for users.
Triggering the node removal much faster, specifically after 1 second ("inter 1s" with no "fall") is better for operators.
Prior discussions around this can be seen at https:/
summary: |
- Improve mysql failover time in HA deployments + Improve failed mysql node removal time in HA deployments |
description: | updated |
To post a comment you must log in.
Proposed https:/ /review. openstack. org/#/c/ 393673/