Understanding Replicator Roles
Replicators can have one of the following roles, master, slave, thl-server, thl-client or
thl-applier.
Replicators within Composite Active/Passive, Composite Active/Active and Composite Dynamic Active/Active clusters can also have the relay role.
masterA replicator in a
masterrole extracts data from a source database (for example, by reading the binary log from a MySQL server), and generates THL. As amasterthe replicator also provides the THL to other replicators over the network connection.slaveA
slavereplicator pulls THL data from amasterand then applies that data to a target database.relayA
relayreplicator is associated with therelaynode within Composite Active/Passive, Composite Active/Active and Composite Dynamic Active/Active clusters only.It receives and applies locally, THL from the remote active cluster and is then made available for downstream replica nodes within the same cluster.
thl-serverVersion availabilityAvailable in 6.1.0 and later.
A
thl-serverreplicator is a special role that Extractor replicators can be changed to temporarily when a Primary is taken offline.
This will allow downstream Applier replicators to download and apply any THL that hasn't yet been processed by the Applier.To enable this role, first you must place the cluster into MAINTENANCE mode and then issue the following statements:
[object Object]To revert back to the original Extractor role, issue the following
[object Object]thl-clientVersion availabilityAvailable in 6.1.0 and later.
A
thl-clientreplicator is a special role that Applier replicators can be changed to. This will allow the Applier replicator to download any THL available from the upstream Extractor, but does NOT apply the THL to the target database.To enable this role, first you must place the cluster into MAINTENANCE mode and then issue the following statements:
[object Object]To revert back to the original Applier role, issue the following:
[object Object]thl-applierVersion availabilityAvailable in 7.0.2 and later.
A
thl-applierreplicator is a special role that applier replicators can be changed to temporarily when a Primary is taken offline. This will allow downstream applier replicators to apply any locally available THL that hasn't yet been processed by the applier.To enable this role, first you must place the cluster into MAINTENANCE mode and then issue the following statements:
[object Object]To revert back to the original role, issue the following
[object Object]