9 messages in com.mysql.lists.bugsReplication Bug in 3.23.33| From | Sent On | Attachments |
|---|---|---|
| Matt Hahnfeld | 14 Feb 2001 08:19 | |
| Sasha Pachev | 14 Feb 2001 11:49 | |
| Sasha Pachev | 14 Feb 2001 12:53 | |
| Ondrej Koala Vacha | 15 Feb 2001 08:38 | |
| Michael Widenius | 15 Feb 2001 11:17 | |
| Ondrej Koala Vacha | 15 Feb 2001 12:51 | |
| Sasha Pachev | 15 Feb 2001 17:44 | |
| Rodolfo Sikora | 15 Feb 2001 17:50 | |
| Michael Widenius | 15 Feb 2001 22:12 |
| Subject: | Replication Bug in 3.23.33 |
|---|---|
| From: | Matt Hahnfeld (hahn...@everysoft.com) |
| Date: | 02/14/2001 08:19:14 AM |
| List: | com.mysql.lists.bugs |
After downgrading to 3.23.30, replication worked fine without the problem posted below. This appears to be a bug in the newest version (3.23.33) only.
The failed tests were run under mysql-3.23.33-pc-linux-gnu-i686 (binary distribution).
The same tests succeeded under mysql-3.23.30-gamma-pc-linux-gnu-i686 (binary distribution) with no problems.
---------- Forwarded message ---------- Date: Tue, 13 Feb 2001 14:33:47 -0500 (EST) From: Matt Hahnfeld <hahn...@everysoft.com> To: mys...@lists.mysql.com Subject: Strange Replication Problem in 3.23.33 (bug?)
I set up two MySQL servers to run in a failover configuration. Because queries will only ever be submitted to one server at a time, I decided to use a makeshift two-way replication scheme under MySQL as descibed in the MySQL manual.
First server (wallace) has this:
-------------------------------- server-id=1 log-bin master-host=gromit master-user=repl master-password=<password> log-slave-updates
--------------------------------
Second server (gromit) has this:
-------------------------------- server-id=2 log-bin master-host=wallace master-user=repl master-password=<password> log-slave-updates
--------------------------------
I started by mirroring both data directories. Then I started both servers and all looked fine. Logs indicate no errors. When I inserted some data on wallace, gromit replicated them just fine. But when I tried to insert data on gromit, wallace never got the changes. The weird thing is, no real errors appeared in the logs.
Then I did a "SHOW SLAVE STATUS" on wallace and saw "Skip_counter" was set to 4294967295!!! Strange, I thought, so I ran "STOP SLAVE", "SET SQL_SLAVE_SKIP_COUNTER=0", and "START SLAVE" on wallace. Suddenly changes made on gromit were reflected on wallace.
But then I tried to insert data on wallace again and the same thing happened. This time gromit never got the changes. When I ran "SHOW SLAVE STATUS" on gromit, it indicated 4294967293. To get it to work, I had to run "SET SQL_SLAVE_SKIP_COUNTER=0" on gromit.
I just don't get it... Why are the skip counters being reset to thse crazy high numbers?
Matt Hahnfeld EverySoft