Bug #41188 | rpl_ndb_denote_gap fails sporadically: wrong Last_IO_Error | ||
---|---|---|---|
Submitted: | 2 Dec 2008 20:19 | Modified: | 30 Jan 2009 18:03 |
Reporter: | Sven Sandberg | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Tests: Replication | Severity: | S7 (Test Cases) |
Version: | 6.0-rpl | OS: | Any |
Assigned to: | Zhenxing He | CPU Architecture: | Any |
Tags: | 6.0-rpl-green, pushbuild, rpl_ndb_denote_gap, test failure |
[2 Dec 2008 20:19]
Sven Sandberg
[18 Dec 2008 6:35]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/61928 2737 He Zhenxing 2008-12-18 BUG#41188 rpl_ndb_denote_gap fails sporadically: wrong Last_IO_Error When master shuts down, the slave I/O thread can fail due to various reasons, and result in various error code and message, for example: 1) reconnect error 2) error in get_master_version_and_clock 3) error in register_slave_on_master The actual situation can be more complicated than this. There are some other problems with this test case: 1) in include/wait_until_disconnected.inc, which set the mysql_errno to a wrong value 2) waiting for reconnection on the wrong host 3) did not start slave after slave stops, and the reason why it worked was because when SHOW SLAVE STATUS says I/O slave is not running, it can be RUN_NOT_CONNECT and reconnecting, so when the master later comes up soon enough, it will reconnect to the master. This patch fixes the problem by: 1) removing I/O thread error code and message because they varies and are not important to this test 2) adding missing --connection master before waiting reconnection to master 3) starting slave IO thread before waiting for SQL thread to stop 4) adding warning suppression for slave I/O thread
[19 Dec 2008 5:43]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/62040 2737 He Zhenxing 2008-12-19 BUG#41188 rpl_ndb_denote_gap fails sporadically: wrong Last_IO_Error When master shuts down, the slave I/O thread can fail due to various reasons, and result in various error code and message, for example: 1) reconnect error 2) error in get_master_version_and_clock 3) error in register_slave_on_master The actual situation can be more complicated than this. There are some other problems with this test case: 1) in include/wait_until_disconnected.inc, which set the mysql_errno to a wrong value 2) waiting for reconnection on the wrong host 3) did not start slave after slave stops, and the reason why it worked was because when SHOW SLAVE STATUS says I/O slave is not running, it can be RUN_NOT_CONNECT and reconnecting, so when the master later comes up soon enough, it will reconnect to the master. This patch fixes the problem by: 1) removing I/O thread error code and message because they varies and are not important to this test 2) adding missing --connection master before waiting reconnection to master 3) starting slave IO thread before waiting for SQL thread to stop 4) adding warning suppression for slave I/O thread
[29 Dec 2008 9:17]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/62395 2773 He Zhenxing 2008-12-29 BUG#41188 rpl_ndb_denote_gap fails sporadically: wrong Last_IO_Error When master shuts down, the slave I/O thread can fail due to various reasons, and result in various error code and message, for example: 1) reconnect error 2) error in get_master_version_and_clock 3) error in register_slave_on_master The actual situation can be more complicated than this. There are some other problems with this test case: 1) in include/wait_until_disconnected.inc, which set the mysql_errno to a wrong value 2) waiting for reconnection on the wrong host 3) did not start slave after slave stops, and the reason why it worked was because when SHOW SLAVE STATUS says I/O slave is not running, it can be RUN_NOT_CONNECT and reconnecting, so when the master later comes up soon enough, it will reconnect to the master. This patch fixes the problem by: 1) removing I/O thread error code and message because they varies and are not important to this test 2) adding missing --connection master before waiting reconnection to master 3) starting slave IO thread before waiting for SQL thread to stop 4) adding warning suppression for slave I/O thread
[9 Jan 2009 8:34]
Zhenxing He
pushed to 6.0-rpl
[30 Jan 2009 13:30]
Bugs System
Pushed into 6.0.10-alpha (revid:luis.soares@sun.com-20090129165607-wiskabxm948yx463) (version source revid:luis.soares@sun.com-20090129163120-e2ntks4wgpqde6zt) (merge vers: 6.0.10-alpha) (pib:6)
[30 Jan 2009 18:03]
Paul DuBois
Test case changes. No changelog entry needed.