Follow these steps to reset replication for an entire dataservice. The current Primary will remain the Primary. Use the switch after completion to change the Primary.
The procedure in this section is specific to a single cluster only. Do not follow this if Composite clusters are in use.
See Section 6.11.7, “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 Cluster will not attempt to automatically recover the
service.
cctrl> set policy maintenancePut each Tungsten Connector offline:
cctrl> router * offlineThis step is essential if applications are still active. Allowing data changes during this process could result in data loss.
Ideally, all applications activity should be suspended until these steps are complete.
On each datasource, reset the service:
shell>trepctl offlineshell>trepctl reset -all -y
The connectors 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 Primary must be reprovisioned. Use the tprovision tool to reprovision from the Primary or valid Replica server.