ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-02-14 14:42:32 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Finding the replica with the most advanced replication index (#1072)

Browse Source
This commit is contained in:
Thomas Schroeter 2018-06-26 11:07:16 +01:00 committed by GitHub
parent b0946f0a97
commit a70ed52e87
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/source/running-a-notary-cluster/operating-percona.rst
View File

@ -117,10 +117,12 @@ When all nodes of the cluster are down, manual intervention is needed to bring
the cluster back up. On the node with the most advanced replication index,
``set safe_to_bootstrap: 1`` in the file ``grastate.dat`` in the data directory.
You can use ``SHOW GLOBAL STATUS LIKE 'wsrep_last_committed';`` to find out the
sequence number of the last committed transaction. Start the first node using
sequence number of the last committed transaction. Or, if MySQL is down, use
``mysqld_safe --wsrep-recover``. This command prints the recovered position.
Once you have found the most advanced node, start that node using
``/etc/init.d/mysql bootstrap-pxc``. Bring back one node at a time and watch
the logs. If a SST is required, the first node can only
serve as a donor for one node a time.
the logs. If a SST is required, the first node can only serve as a donor for
one node a time.
See the documentation of the safe to bootstrap feature. Similar to restoring
from backup, restarting the entire cluster is an operation that deserves