openstack/charm-mysql-innodb-cluster
Code Issues Proposed changes

Documentation improvements

Browse Source 
Change-Id: Iee0e307203c4a12e78097321cd5e446e77ab0a76
Related-Bug: #1926460
This commit is contained in:
Aurelien Lourot
2021-09-07 14:18:35 +02:00
parent 488ce8815e
commit 311ae13fd5
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
src/README.md
View File

@@ -60,12 +60,12 @@ See the [vault][vault-charm-readme] charm README for more information.
## Adding a unit on a new subnet ## Adding a unit on a new subnet
If a new unit is added after the cluster has already formed and the new unit When adding a unit to an already formed cluster, and where that unit resides on
is on different subnet to any of the existing units then the following actions a subnet different from any existing unit, the following extra actions are
are needed to add the unit to the cluster: needed:
juju run-action mysql-innodb-cluster/leader update-unit-acls juju run-action --wait mysql-innodb-cluster/leader update-unit-acls
juju run-action mysql-innodb-cluster/leader add-instance address=<address of new unit> juju run-action --wait mysql-innodb-cluster/leader add-instance address=<address of new unit>
## Actions ## Actions