Bug #35702 | setting SQL_SLAVE_SKIP_COUNTER does not work on solaris | ||
---|---|---|---|
Submitted: | 31 Mar 2008 11:02 | Modified: | 30 Apr 2008 12:07 |
Reporter: | Salman Rawala | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: General | Severity: | S2 (Serious) |
Version: | 5.1.22 | OS: | Solaris (Sun Solaris 10) |
Assigned to: | CPU Architecture: | Any | |
Tags: | master, replication, skip replication statement, slave, slave replication skip |
[31 Mar 2008 11:02]
Salman Rawala
[31 Mar 2008 12:07]
Sveta Smirnova
Thank you for the report. Please add select * from t1; between STOP SLAVE SQL_THREAD; and SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;: STOP SLAVE SQL_THREAD; select * from t1; SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; Table can exists on slave before you run SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; Also please note this statement skips the next N events (not only queries) from the master. See also http://dev.mysql.com/doc/refman/5.1/en/set-global-sql-slave-skip-counter.html
[1 May 2008 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".