Update HAProxy default timeout values
The default HAProxy timeout values are fairly strict. On a busy cloud it is common to exceed one or more of these timeouts. The only indication that HAProxy has exceeded a timeout and dropped the connection is errors such as "BadStatusLine" or "EOF." These can be very difficult to diagnose when intermittent. This charm-helpers sync pulls in the change to update the default timeout values to more real world settings. These values have been extensively tested in ServerStack. Configured values will not be overridden. Partial Bug: #1736171 Change-Id: I973962a5c1538b0d9afbebea8cebf50d938ecfb5
Showing
- charmhelpers/contrib/openstack/amulet/utils.py 6 additions, 3 deletionscharmhelpers/contrib/openstack/amulet/utils.py
- charmhelpers/contrib/openstack/context.py 13 additions, 1 deletioncharmhelpers/contrib/openstack/context.py
- charmhelpers/contrib/openstack/templates/haproxy.cfg 4 additions, 4 deletionscharmhelpers/contrib/openstack/templates/haproxy.cfg
- charmhelpers/contrib/openstack/utils.py 2 additions, 0 deletionscharmhelpers/contrib/openstack/utils.py
- charmhelpers/contrib/storage/linux/ceph.py 4 additions, 4 deletionscharmhelpers/contrib/storage/linux/ceph.py
- charmhelpers/contrib/storage/linux/lvm.py 50 additions, 0 deletionscharmhelpers/contrib/storage/linux/lvm.py
- charmhelpers/core/host.py 2 additions, 0 deletionscharmhelpers/core/host.py
- charmhelpers/core/host_factory/ubuntu.py 1 addition, 0 deletionscharmhelpers/core/host_factory/ubuntu.py
- config.yaml 4 additions, 4 deletionsconfig.yaml
- tests/charmhelpers/contrib/openstack/amulet/utils.py 6 additions, 3 deletionstests/charmhelpers/contrib/openstack/amulet/utils.py
- tests/charmhelpers/core/host.py 2 additions, 0 deletionstests/charmhelpers/core/host.py
- tests/charmhelpers/core/host_factory/ubuntu.py 1 addition, 0 deletionstests/charmhelpers/core/host_factory/ubuntu.py
Loading
Please register or sign in to comment