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.
If you are upgrading MySQL from any 5.x release to version 8.x, and plan to maintain replication, you
may encounter errors due to differences in SQL_MODEs and collations. To avoid such errors you will
need to make temporary use of two additional filters, dropsqlmode and
mapcharset
After ALL nodes are running the same release of MySQL these filters can be removed.
For a full explanation of this, see Section 6.15.6, “Upgrading between MySQL 5.x and MySQL 8.x”
For maintenance operations on a Primary, the current Primary should be switched, the required maintenance steps performed, and then the Primary switched back.
Disable a datasource using the datasource shun command.
Put the replicator offline using trepctl offline.
If you are using the Multi-Site/Active-Active 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 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 Primary that should be replicated.
mysql> SET SESSION SQL_LOG_BIN=0;Restart replication and recover the datasource after maintenance is complete using datasource recover, trepctl online and optionally mm_trepctl online.