Bug #17708 | replication rules fail if table missing on slave | ||
---|---|---|---|
Submitted: | 24 Feb 2006 18:31 | Modified: | 2 May 2006 13:45 |
Reporter: | Bernd Ocklin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0.18-max | OS: | Linux (Linux 2.6.9 i686 RHE4) |
Assigned to: | CPU Architecture: | Any |
[24 Feb 2006 18:31]
Bernd Ocklin
[2 Apr 2006 12:12]
Valeriy Kravchuk
Thank you for a problem report. Sorry, but I was not able to repeat the behaviour you described with 5.0.21-BK version on slave. In error log I've got only: 060402 11:59:03 [Note] Slave I/O thread: connected to master 'repl@127.0.0.1:334 0', replication started in log 'mysql-bin.010' at position 304 060402 11:59:03 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.010' at position 304, relay log './suse-relay-bin.000001' position: 4 while performing both inserts and update - they are all ignored. My configuration was the following: openxs@suse:~/dbs/5.0> cat my.cnf [mysqld] server-id=9 replicate-do-table = test.real1 replicate-ignore-table= test.test1 replicate-ignore-table= test.test2 #character-set-connection=latin1 #collation-connection=latin1_german1_ci openxs@suse:~/dbs/5.0> I was forced to change table name from real to real1, but otherwise my test was similar to those you described. So, please, try ot repeat with a newer version, 5.0.19, and inform about the results.
[2 May 2006 13:35]
Bernd Ocklin
Cool, tested it with 5.0.20 and the error doesn't occur anymore. Obviously: bug was fixed. Thanks.
[2 May 2006 13:45]
MySQL Verification Team
Thank you for the feedback.