Tungsten Replicator 2.2 Manual

Chapter 5. Operations Guide
There are a number of key operations that enable you to monitor and manage your replication cluster. Tungsten Replicator includes a
small number of tools that can help with this process, including the core trepctl command, for controlling the replication system, and
thl, which provides an interface to the Tungsten History Log and information about the changes that have been recorded to the log and
distributed to the slaves.
During the installation process the file /opt/continuent/share/env.sh will have been created which will seed the shell with the necessary
$PATH and other details to more easily manage your cluster. You can load this script manually using:
shell> source /opt/continuent/share/env.sh
Once loaded, all of the tools for controlling and monitoring your replicator installation should be part of your standard PATH.
5.1. Checking Replication Status
To check the replication status you can use the trepctl command. This accepts a number of command-specific verbs that provide status
and control information for your configured cluster. The basic format of the command is:
shell> trepctl [-host hostname] command
The -host option is not required, and enables you to check the status of a different host than the current node.
To get the basic information about the currently configured services on a node and current status, use the services verb command:
shell> trepctl services
Processing services command...
NAME
VALUE
---- -----
appliedLastSeqno: 211
appliedLatency : 17.66
role
: slave
serviceName : firstrep
serviceType : local
started
: true
state
: ONLINE
Finished services command...
In the above example, the output shows the last sequence number and latency of the host, in this case a slave, compared to the master
from which it is processing information. In this example, the last sequence number and the latency between that sequence being
processed on the master and applied to the slave is 17.66 seconds. You can compare this information to that provided by the master,
either by logging into the master and running the same command, or by using the host command-line option:
shell> trepctl -host host1 services
Processing services command...
NAME
VALUE
---- -----
appliedLastSeqno: 365
appliedLatency : 0.614
role
: master
serviceName : firstrep
serviceType : local
started
: true
state
: ONLINE
Finished services command...
By comparing the appliedLastSeqno for the master against the value on the slave, it is possible to determine that the slave and the master
are not yet synchronized.
For a more detailed output of the current status, use the status command, which provides much more detailed output of the current
replication status:
shell> trepctl status
Processing status command...
NAME
VALUE
---- -----
appliedLastEventId : mysql-bin.000064:0000000002757461;0
appliedLastSeqno : 212
appliedLatency : 263.43
channels : 1
clusterName
: default
currentEventId
: NONE
currentTimeMillis : 1365082088916
dataServerHost
: host2
extensions :
latestEpochNumber : 0
125