Master maintenance must be carried out when the master has been switched to a slave, and then shunned. The master can be temporarily switched to a slave, taken out of the dataservice through shunning, and then added back to the dataservice and then switched back again to be the master.
Maintenance on the dataserver should be performed directly on the corresponding server, not through the connector.
The complete sequence and commands required to perform maintenance on an active master are shown in the table below. The table assumes a dataservice with three datasources:
|2||Set the maintenance policy||set policy maintenance||Master||Slave||Slave|
|3||Switch master||switch to host2||Slave||Master||Slave|
Shun ||datasource host1 shun||Shunned||Master||Slave|
Validate the ||tpm validate||Shunned||Master||Slave|
Recover the slave ( ||datasource host1 recover||Slave||Master||Slave|
|8||Ensure the slave has caught up||Slave||Master||Slave|
Switch master back to
||switch to host1||Master||Slave||Slave|
|10||Set automatic policy||set policy automatic||Master||Slave||Slave|