b0bb8dfa7a
This patch introduces new cluster status "reboot" which is set by leader node hence other nodes will start mysql without "--wsrep-new-cluster" option. Before this following situation took place: All pods go down one by one with some offset; First and second nodes have max seqno; The script on the first node detects there are no active backends and starts timeout loop; The script on the second node detects there are no active backends and starts timeout loop (with approx. 20 sec offset from first node) ; Timeout loop finishes on first node, it checks highest seqno and lowest hostname and wins the ability to start cluster. Mysql is started with “--wsrep-new-cluster” parameter. Seqno is set to “-1” for this node after mysql startup; Periodic job syncs values from grastate file to configmap; Timeout loop finishes on second node. It checks node with highest seqno and lowest hostname and since seqno is already “-1” for first node, the second node decides that it should lead the cluster startup and executes mysql with “--wsrep-new-cluster” option as well which leads to split brain Change-Id: Ic63fd916289cb05411544cb33d5fdeed1352b380
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
Communication
- Join us on Slack - #openstack-helm
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-4 on freenode
- Meeting Agenda Items: Agenda
Launchpad
Bugs and blueprints are tracked via OpenStack-Helm's Launchpad. Any bugs or blueprints filed in the OpenStack-Helm-Infra Launchpad will be closed and requests will be made to file them in the appropriate location.