5.14. Performing Database or OS Maintenance
When performing database or operating system maintenance, datasources
should be temporarily removed from the dataservice and the replicator
should be disabled. Follow these rules for the best results. Detailed
steps are provided below for different scenarios.
For maintenance operations on a master, the current master should be
switched, the required maintenance steps performed, and then the
master switched back.
Disable a datasource using the datasource
Put the replicator offline using trepctl offline.
If you are using the Multisite/Multimaster topology, put the extra
replicator offline using mm_trepctl offline. The
mm_trepctl alias will only work if you configured
Tungsten Replicator with the
--executable-prefix=mm (in [Tungsten Replicator 2.2 Manual]) option.
When making changes to a MySQL system the binary log should be
disabled for your session. This will prevent corrective actions from
replicating to other servers. Ignore this suggestion if you are making
changes to a master that should be replicated.
SET SESSION SQL_LOG_BIN=0;
Restart replication and recover the datasource after maintenance is
complete using datasource
recover, trepctl online and optionally