Red Hat Bugzilla – Bug 1281745
Updates to HAProxy configuration
Last modified: 2016-04-07 17:12:10 EDT
Description of problem:
Based on recent field engagements, we need to update the HAProxy configuration. The things that we need to ensure:
stick-table type ip size should be 1000
timeout client 60m # or higher
timeout server 60m # or higher
on the following lines:
server * check inter 1s port 9200 on-marked-down shutdown-sessions
need to include "backup" keyword
Version-Release number of selected component (if applicable):
Can you confirm the absence of the backup keyword renders the failover useless? If that's not the case, can you explain what the impact is?
upstream bug report https://bugs.launchpad.net/tripleo/+bug/1530897
and upstream review for the client/server timeout which afaics is the main missing thing https://review.openstack.org/#/c/263308/
The "stick-table type ip size" thing and backup are both addressed in https://review.openstack.org/#/c/194960/4/manifests/loadbalancer.pp
The only thing still missing afaics upstream is the client/server timeouts, still 0 at https://github.com/openstack/puppet-tripleo/blob/dafdc1f4efde8c57a8c7160ae0162866496089dc/manifests/loadbalancer.pp#L923
the fix at https://review.openstack.org/#/c/263308 abandoned in favor of https://review.openstack.org/#/c/223223 which is merged now (and sets to 90m)
new timeouts are set on controllers
bind 172.17.1.11:3306 transparent
stick on dst
stick-table type ip size 1000
timeout client 90m
timeout server 90m
server overcloud-controller-0 172.17.1.13:3306 backup check fall 5 inter 2000 on-marked-down shutdown-sessions port 9200 rise 2
server overcloud-controller-1 172.17.1.15:3306 backup check fall 5 inter 2000 on-marked-down shutdown-sessions port 9200 rise 2
server overcloud-controller-2 172.17.1.14:3306 backup check fall 5 inter 2000 on-marked-down shutdown-sessions port 9200 rise 2
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.