openstack
/
openstack-ansible
Code Issues Proposed changes

Change the galera health check for better cluster health 

The current galera cluster health check simply logs into a cluster node
but does not check if the node is sync'd. This can lead to an issue
where a node is placed back into the pool before it is ready. If this
happens it can lead to a broken OpenStack environment until the wsrep
received queue is processed which is especially true if the node out of
sync happens to be the primary.

Change-Id: I49e371a2743618a0b5544a23e892aa28bb8567eb
Closes-Bug: #1665667
Depends-On: Ie1b3b9724dd33de1d90634166e585ecceb1f4c96
Depends-On: I81c924464aa4b19c2a62f37b5bf26c3c0453786a
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
This commit is contained in:
Kevin Carter 2017-11-16 11:59:21 -06:00 committed by Kevin Carter (cloudnull)
parent e82ca47a84
commit 7b3aac28a0
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
group_vars/haproxy_all/haproxy.yml
View File

@ -44,11 +44,12 @@ haproxy_default_services:
haproxy_backup_nodes: "{{ (groups['galera_all'] | default([]))[1:] }}"
haproxy_bind: "{{ [internal_lb_vip_address] }}"
haproxy_port: 3306
haproxy_check_port: 9200
haproxy_balance_type: tcp
haproxy_timeout_client: 5000s
haproxy_timeout_server: 5000s
haproxy_backend_options:
- "mysql-check user {{ galera_monitoring_user }}"
- "httpchk HEAD /"
haproxy_whitelist_networks: "{{ haproxy_galera_whitelist_networks }}"
- service:
haproxy_service_name: repo_git