[RFE] Kolla-Ansible should stop and deploy Galera safely

Bug #1831120 reported by Pierre Riteau
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kolla-ansible
Confirmed
Wishlist
Unassigned

Bug Description

The Galera documentation explains how it is possible to restart a cluster safely by making sure the most advanced node is started first: http://galeracluster.com/documentation-webpages/restartingcluster.html

We should make sure `kolla-ansible stop` stops running Galera containers in a specific order so that the most advanced node is identified.

Then `kolla-ansible deploy` could be tuned to restart Galera using the most advanced node first, which would hopefully remove the requirement of running the mariadb_recovery command. At the very least it would help identifying which node to use as `mariadb_recover_inventory_name`.

summary: - Kolla-Ansible should stop and deploy Galera safely
+ [RFE] Kolla-Ansible should stop and deploy Galera safely
Changed in kolla-ansible:
importance: Undecided → Wishlist
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.