| Bug #49191 | rpl_get_master_version_and_clock failed on PB2: COM_REGISTER_SLAVE failed | ||
|---|---|---|---|
| Submitted: | 30 Nov 2009 1:20 | Modified: | 15 Mar 2010 4:23 |
| Reporter: | Luis Soares | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Tests: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.1 | OS: | Any |
| Assigned to: | Daogang Qu | CPU Architecture: | Any |
[1 Dec 2009 8:28]
Daogang Qu
The 'rpl_get_master_version_and_clock' test case is added to experimental test list due to the bug#49191.
[24 Dec 2009 7:33]
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/95634 3296 Dao-Gang.Qu@sun.com 2009-12-24 Bug #49191 rpl_get_master_version_and_clock failed on PB2: COM_REGISTER_SLAVE failed The 'rpl_get_master_version_and_clock' test verifies if the slave I/O thread tries to reconnect to master when it tries to get the values of the UNIX_TIMESTAMP, SERVER_ID from master under network disconnection. So the master server is restarted for making the transient network disconnection, during the period the COM_REGISTER_SLAVE failures are produced in server log file when the slave I/O thread tries to register on master. To fix the problem, suppress COM_REGISTER_SLAVE failures in server log file by mtr suppression, because they are expected. @ mysql-test/suite/rpl/t/rpl_get_master_version_and_clock-slave.opt Increase the master retry count, so that the slave I/O thread has enough time to reconnect master successfully.
[27 Jan 2010 2:55]
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/98271 3335 Dao-Gang.Qu@sun.com 2010-01-27 Bug #49191 rpl_get_master_version_and_clock failed on PB2: COM_REGISTER_SLAVE failed The 'rpl_get_master_version_and_clock' test verifies if the slave I/O thread tries to reconnect to master when it tries to get the values of the UNIX_TIMESTAMP, SERVER_ID from master under network disconnection. So the master server is restarted for making the transient network disconnection, during the period the COM_REGISTER_SLAVE failures are produced in server log file when the slave I/O thread tries to register on master. To fix the problem, suppress COM_REGISTER_SLAVE failures in server log file by mtr suppression, because they are expected. @ mysql-test/suite/rpl/r/rpl_get_master_version_and_clock.result Removed mtr.add_suppression("Get master clock failed with error: ") and mtr.add_suppression("Get master SERVER_ID failed with error: "). Because they are suppressed globally.
[27 Jan 2010 3:42]
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/98272 3849 Dao-Gang.Qu@sun.com 2010-01-27 [merge] Bug #49191 rpl_get_master_version_and_clock failed on PB2: COM_REGISTER_SLAVE failed The 'rpl_get_master_version_and_clock' test verifies if the slave I/O thread tries to reconnect to master when it tries to get the values of the UNIX_TIMESTAMP, SERVER_ID from master under network disconnection. So the master server is restarted for making the transient network disconnection, during the period the COM_REGISTER_SLAVE failures are produced in server log file when the slave I/O thread tries to register on master. To fix the problem, suppress COM_REGISTER_SLAVE failures in server log file by mtr suppression, because they are expected. @ mysql-test/suite/rpl/t/rpl_get_master_version_and_clock.test Removed mtr.add_suppression("Get master clock failed with error: ") and mtr.add_suppression("Get master SERVER_ID failed with error: "). Because they are suppressed globally.
[27 Jan 2010 7:59]
Daogang Qu
Pushed into mysql-5.1-bugteam and mysql-pe.
[4 Feb 2010 10:20]
Bugs System
Pushed into 5.1.44 (revid:joro@sun.com-20100204101444-2j32mhqroo0iiio6) (version source revid:aelkin@mysql.com-20100128095157-dkwe8691qj2tp9h7) (merge vers: 5.1.43) (pib:16)
[4 Feb 2010 13:33]
Jon Stephens
Change in test code only, no end-user changes to document. Closed without further action.
[5 Feb 2010 11:49]
Bugs System
Pushed into mysql-next-mr (revid:alik@sun.com-20100204063540-9czpdmpixi3iw2yb) (version source revid:alik@sun.com-20100130212638-ai8t5v3u6647p6d2) (pib:16)
[5 Feb 2010 11:56]
Bugs System
Pushed into 6.0.14-alpha (revid:alik@sun.com-20100205113942-oqovjy0eoqbarn7i) (version source revid:alik@sun.com-20100204064210-ljwanqvrjs83s1gq) (merge vers: 6.0.14-alpha) (pib:16)
[5 Feb 2010 12:01]
Bugs System
Pushed into 5.5.2-m2 (revid:alik@sun.com-20100203172258-1n5dsotny40yufxw) (version source revid:alik@sun.com-20100130191336-i53i9wx67n81ridm) (merge vers: 5.5.2-m2) (pib:16)
[5 Feb 2010 13:27]
Jon Stephens
Affected tests only; no user-facing changes to document. Closed.
[12 Mar 2010 14:09]
Bugs System
Pushed into 5.1.44-ndb-7.0.14 (revid:jonas@mysql.com-20100312135944-t0z8s1da2orvl66x) (version source revid:jonas@mysql.com-20100312115609-woou0te4a6s4ae9y) (merge vers: 5.1.44-ndb-7.0.14) (pib:16)
[12 Mar 2010 14:25]
Bugs System
Pushed into 5.1.44-ndb-6.2.19 (revid:jonas@mysql.com-20100312134846-tuqhd9w3tv4xgl3d) (version source revid:jonas@mysql.com-20100312060623-mx6407w2vx76h3by) (merge vers: 5.1.44-ndb-6.2.19) (pib:16)
[12 Mar 2010 14:38]
Bugs System
Pushed into 5.1.44-ndb-6.3.33 (revid:jonas@mysql.com-20100312135724-xcw8vw2lu3mijrhn) (version source revid:jonas@mysql.com-20100312103652-snkltsd197l7q2yg) (merge vers: 5.1.44-ndb-6.3.33) (pib:16)
[15 Mar 2010 4:23]
Jon Stephens
Closed. See my previous comments.
Description: rpl_get_master_version_and_clock failed on PB2: rpl.rpl_get_master_version_and_clock 'mix' [ fail ] Found warnings/errors in server log file! Test ended at 2009-11-27 20:48:56 mysqltest: Logging to ''. mysqltest: Results saved in ''. mysqltest: Connecting to server localhost:13021 (socket /export/home/pb2/build/sb_0-None-1259342497.59/tmp/cFxPk7klZz/mysqld.2.sock) as 'root', connection 'default', attempt 0 ... mysqltest: ... Connected. mysqltest: Start processing test commands from './include/check-warnings.test' ... line 091127 22:48:52 [Warning] Slave I/O: Master command COM_REGISTER_SLAVE failed: failed registering on master, reconnecting to try again, log 'master-bin.000001' at postion 4, Error_code: 1597 091127 22:48:54 [Warning] Slave I/O: Master command COM_REGISTER_SLAVE failed: failed registering on master, reconnecting to try again, log 'master-bin.000001' at postion 106, Error_code: 1597 ^ Found warnings in /export/home/pb2/build/sb_0-None-1259342497.59/mysql-5.1-bugteam-gcov/mysql-test/var/log/mysqld.2.err mysqltest: ... Done processing test commands. mysqltest: Test has succeeded! ok - saving '/export/home/pb2/build/sb_0-None-1259342497.59/mysql-5.1-bugteam-gcov/mysql-test/var/log/rpl.rpl_get_master_version_and_clock-mix/' to '/export/home/pb2/build/sb_0-None-1259342497.59/mysql-5.1-bugteam-gcov/mysql-test/var/log/rpl.rpl_get_master_version_and_clock-mix/' Retrying test, attempt(2/3)... Failure details: Where Build Test Run Suite Case Mode When mysql-5.1-bugteam 716497 tree-gcov-linux-x86_64-tar-gz 717783 tyr36 tree-gcov-linux-x86_64-tar-gz 717783 tyr36 ps rpl rpl_get_master_version_and_clock mix 2009-11-27 17:19:30 How to repeat: See: http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&search=yes&push_id=71649... Suggested fix: n/a