W/o this patch, haproxy daemon under load never can
be stopped gracefully and it also may exceed given stop/monitor
timeouts ending up being restarted by pacemaker.
The solution is:
* increase haproxy resource monitor/stop timeout and interval
* fix stop action for OCF to not rely on kill command exit codes
* wrap kill in retries and issue a SIGKILL only if there are no more
retries left for gracefull termination
* add debug parameter for haproxy RA OCF script and provide more
logging as well
* set debug for haproxy RA, if global debug is enabled
Reviewed: https:/ /review. openstack. org/160399 /git.openstack. org/cgit/ stackforge/ fuel-library/ commit/ ?id=2eea7abdf6e 5bbff2c6369a10a b2dba74eda31c7
Committed: https:/
Submitter: Jenkins
Branch: stable/6.0
commit 2eea7abdf6e5bbf f2c6369a10ab2db a74eda31c7
Author: Bogdan Dobrelya <email address hidden>
Date: Wed Feb 25 17:53:22 2015 +0100
Adjust stop/monitor and fix kill for ns_haproxy
W/o this patch, haproxy daemon under load never can
be stopped gracefully and it also may exceed given stop/monitor
timeouts ending up being restarted by pacemaker.
The solution is:
* increase haproxy resource monitor/stop timeout and interval
* fix stop action for OCF to not rely on kill command exit codes
* wrap kill in retries and issue a SIGKILL only if there are no more
retries left for gracefull termination
* add debug parameter for haproxy RA OCF script and provide more
logging as well
* set debug for haproxy RA, if global debug is enabled
Closes-bug: #1424959
Related-bug: #1425579
Change-Id: I7ab6dc2341821c 3b82ef3d3ac63b6 4a5a9958fa9
Signed-off-by: Bogdan Dobrelya <email address hidden>