daz bdb856c8fe [docs] Migrate ops and appendix content

1. Migrate Ops chapter and tips and tricks appendix to developer docs
2. Migrate Appendix G to a chapter in the developer docs
3. Minor edits

Change-Id: I4070f02b75a8f9614545be0744e63ba76a3b49e2
Implements: blueprint osa-install-guide-overhaul

2016-06-17 10:13:27 +10:00

1.3 KiB

Raw Blame History

Home OpenStack-Ansible Installation Guide

Removing nodes

In the following example, all but one node was shut down gracefully:

# ansible galera_container -m shell -a "mysql -h localhost \
-e 'show status like \"%wsrep_cluster_%\";'"
node3_galera_container-3ea2cbd3 | FAILED | rc=1 >>
ERROR 2002 (HY000): Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2)

node2_galera_container-49a47d25 | FAILED | rc=1 >>
ERROR 2002 (HY000): Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2)

node4_galera_container-76275635 | success | rc=0 >>
Variable_name             Value
wsrep_cluster_conf_id     7
wsrep_cluster_size        1
wsrep_cluster_state_uuid  338b06b0-2948-11e4-9d06-bef42f6c52f1
wsrep_cluster_status      Primary

Compare this example output with the output from the multi-node failure scenario where the remaining operational node is non-primary and stops processing SQL requests. Gracefully shutting down the MariaDB service on all but one node allows the remaining operational node to continue processing SQL requests. When gracefully shutting down multiple nodes, perform the actions sequentially to retain operation.

1.3 KiB Raw Blame History

Removing nodes

1.3 KiB

Raw Blame History