Databases Reference
In-Depth Information
Controlling a slave server
Here we will assume that the Sandbox testing environment has been set. However,
the explanations are useful for all situations in which we have a slave server. After
connecting to a slave and once again opening the
Replication
menu, we see:
The following options are available:
• The
See slave status table
link permits us to receive information about all the
system variables related to replication for this slave server.
• The
Control slave:
link reveals more options; some of them can toggle
between the stop and start condition:
° The
Full stop
option is used to stop both the IO thread (the part of
the MySQL server responsible for receiving updates from the master
and writing them to the slave's relay log) and the SQL thread (which
reads the updates from the relay log and executes them)
° The
Reset slave
option stops the slave, sends a
RESET SLAVE
command that causes it to forget its replication position in the
master's binary log, and then restarts the slave
° The
SQL Thread Stop only
option and
IO Thread Stop only
option
are used to stop just the respective thread
• The
Error management:
link permits to tell the slave server to skip some of
the events (updates) sent from the master. For more details
, please refer to
skip-counter.html
.
• The
Change or reconfigure master server
link could be used to specify that
this slave server should now receive updates from a different master.
Search WWH ::
Custom Search