Bug #3641 | slave not receiving updates | ||
---|---|---|---|
Submitted: | 3 May 2004 23:37 | Modified: | 5 May 2004 16:51 |
Reporter: | John Budnichuk | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | 4.0.18 | OS: | Solaris (Solaris 8) |
Assigned to: | Timothy Smith | CPU Architecture: | Any |
[3 May 2004 23:37]
John Budnichuk
[4 May 2004 2:17]
John Budnichuk
It appears if I drop the database name and table on the slave then issue a stop/start slave all appears well now. The slave server wants to create the table name without IF NOT EXISTS..Can someone further clarify what is happening?
[5 May 2004 16:51]
Timothy Smith
There isn't enough information for me to repeat this problem. Please see our manual for help in making a reproducable test case. I know it is harder with replication setups.... This sounds like you simply had a table on the slave that was not yet created on the master at the time when replication started. When that table was created on the master, the slave tried to create it and got an error. This is the expected behavior, and is desirable - the slave and master should be in sync at all times, or else the replication will not work. If this is not the case, you'll need to provide more information. For example, SHOW SLAVE STATUS\G (on the slave), and also the exact query that the slave is trying to run (use mysqlbinlog --position=NNNN, where NNNN is taken from the SHOW SLAVE STATUS relay_log_pos). Thank you.