89514

89514



Slave Errors During Replication

If a statement produces the same error (identical error codę) on both the master and the slave, the

error is logged, but replication continues.

If a statement produces different errors on the master and the slave, the slave SQL thread terminates,

and the slave writes a message to its error log and waits for the database administrator to decide what

to do about the error. This includes the case that a statement produces an error on the master or the

slave, but not both. To address the issue, connect to the slave manually and determine the cause of

the problem. SHOW SLAVE STATUS is useful for this. Then fix the problem and run

START SLAVE. For

example, you might need to create a nonexistent table before you can start the slave again.

If this error codę validation behavior is not desirable, some or all errors can be masked out (ignored)

with the —slave-skip-errors [2021] option.

For nontransactional storage engines such as My ISAM, it is possible to have a statement that only

partially updates a table and returns an error codę. This can happen, for example, on a multiple-row

insert that has one rowviolating a key constraint, or if a long update statement is killed after updating

some of the rows. If that happens on the master, the slave expects execution of the statement to resułt

in the same error codę. If it does not, the slave SQL thread stops as described previously.

If you are replicating between tables that use different storage engines on the master and slave, keep

in mind that the same statement might produce a different error when run against one version of the

table, but not the other, or might cause an error for one version of the table, but not the other. For

example, sińce My ISAM ignores foreign key constraints, an INSERT or UPDATE statement accessing

an InnoDB table on the master might cause a foreign key violation but the same statement performed

on a My ISAM version of the same table on the slave would produce no such error, causing replication to stop.



Wyszukiwarka

Podobne podstrony:
Replication Relay and Status Logs During replication, a slave server creates several logs that hołd
Creating a User for Replication Each slave must connect to the master using a MySQL user name and pa
Direct the slave to use the master. Instruct the slave to use the master as the replication data sou
Replication and Server SQL Modę Using different server SQL modę settings on the master and the slave
Replication and Time Zones The same system time zonę should be set for both master and slave. Otherw
Replication of Columns Having Different Data Types Corresponding columns on the master s and the sla
Replication of current_user() The foliowing statements support use of the CURRENTJJSER () [1287] fun
Replication with Morę Columns on Master or Slave You can replicate a table from the master to the sl
start. 6.    Configure the slave with the replication coordinates from the master. Th
Using different storage engines on master and slave. It is possible to replicate transactional table
Using Replication for Backups To use replication as a backup solution, replicate data from the maste
00114 ?a8afe54cef5892f75743697dafe07d 114 McWilliams would be if used as the finał value, and teste
00268 ?a148167663d78e6679e602ee961c3b 270 Montgomery experiments are often used in the design and/o
img044 (59) FOUR SIMPLE HANDKERCHIEF EDGINGSEDGING B_ This is a very simple little edging which, if
172 Aneta Wszelaki DIFFERENCES IN THE PREPARATION OF THE FINANCIAL STATEMENTS OF THE BANK ACCORDING
MR293R19072 1 The opftratiojis doscribed below sr« to be carri M out on both the right and left ban

więcej podobnych podstron