Follow these steps to reset replication for an entire dataservice. The current master will remain the master. Use the switch after completion to change the master.
The procedures in this section are designed for the pre-v6.x Multisite/Multimaster topology ONLY. Do NOT use these procedures with version 6.x Multisite Clusters.
For version 6.x Multisite Clustering, please refer to Deploying Composite Multimaster Clustering.
See Section 5.10.6, “Resetting an Entire Dataservice from Filesystem Snapshots” if you would like to restore a file system snapshot to every server as part of this process.
Put the dataservice into
MAINTENANCE mode. This ensures
that Tungsten Clustering will not attempt to automatically recover the
service.
cctrl> set policy maintenanceEnable force mode:
cctrl> set force trueShun each datasource:
cctrl>datasource master shuncctrl>datasource slave1 shuncctrl>datasource slave2 shun
Put each Tungsten Connector offline:
cctrl> router * offlineOn each datasource, reset the service:
shell>trepctl -service east offlineshell>trepctl -service east reset -all -y
Reconfigure the replicator and datasource configuration on each host, starting with the master:
cctrl>set force truecctrl>replicator new-master mastercctrl>replicator new-master onlinecctrl>datasource new-master mastercctrl>datasource new-master onlinecctrl>replicator slave1 slave new-mastercctrl>replicator slave1 onlinecctrl>datasource slave1 slavecctrl>datasource slave1 onlinecctrl>replicator slave2 slave new-mastercctrl>replicator slave2 onlinecctrl>datasource slave2 slavecctrl>datasource slave2 online
The connector can now be re-enabled and the cluster returned to operational state:
cctrl>router * onlinecctrl>set policy automaticcctrl>cluster heartbeat
Any servers not matching the master must be reprovisioned. Use the tungsten_provision_slave tool to reprovision from the master or valid slave server.