| Bug #47982 | rpl_auto_increment failed on PB2 | ||
|---|---|---|---|
| Submitted: | 12 Oct 2009 0:05 | Modified: | 7 Feb 2010 21:33 |
| Reporter: | Luis Soares | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | Tests: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.1 | OS: | Any |
| Assigned to: | Serge Kozlov | CPU Architecture: | Any |
[31 Jan 2010 22:02]
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/98781 3344 Serge Kozlov 2010-02-01 Bug#47982. The reason of bug is engine substitution on slave. InnoDB plugin was unloaded and server replaced InnoDB to MyISAM. The patch disables engine subtsitution by default and if InnoDB plugin fails on slave then slave SQL thread stops with proper error message. modified: mysql-test/extra/rpl_tests/rpl_auto_increment.test
[4 Feb 2010 14:44]
Luis Soares
Hi Serge,
I think you can close this as CAN'T REPEAT.
Arguments:
1. Last test failure with given symptom was in
2009-10-22 11:44:09 - more than 3 months ago.
See: http://tinyurl.com/y8lnmeg
2. The test is happly running green on PB2 for bugteam tree:
rpl.rpl_auto_increment [ pass ] 3973
rpl.rpl_auto_increment 'innodb_plugin' [ pass ] 5104
See: http://tinyurl.com/yd3d9mc
Regards,
Luís
[7 Feb 2010 21:33]
Serge Kozlov
After discuss with Luis I canceled the patch.
Description: Test case failure observed when running with InnoDB plugin. Failure data: Where Build Test Run Suite Case Mode When mysql-5.1-bugteam 571069 binary-max-sol10-sparc64-tar-gz 571193 takk-z5 test-max-sol10-sparc64 571725 tor04-z3 n_mix rpl rpl_auto_increment InnoDB plugin 2009-10-09 19:11:28 Failure symptom: rpl.rpl_auto_increment 'InnoDB plugin' w7 [ fail ] Test ended at 2009-10-09 20:42:03 CURRENT_TEST: rpl.rpl_auto_increment --- /export/home/pb2/test/sb_0-810910-1255113498.34/mysql-5.1.40-solaris10-sparc-test/mysql-test/suite/rpl/r/rpl_auto_increment.result 2009-10-09 20:44:52.000000000 +0300 +++ /export/home/pb2/test/sb_0-810910-1255113498.34/mysql-5.1.40-solaris10-sparc-test/mysql-test/suite/rpl/r/rpl_auto_increment.reject 2009-10-09 21:42:03.651812340 +0300 @@ -242,7 +242,7 @@ t1 CREATE TABLE `t1` ( `id` mediumint(9) NOT NULL AUTO_INCREMENT, PRIMARY KEY (`id`) -) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=latin1 +) ENGINE=MyISAM AUTO_INCREMENT=4 DEFAULT CHARSET=latin1 drop table t1; stop slave; drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9; mysqltest: Result content mismatch - saving '/export/home/pb2/test/sb_0-810910-1255113498.34/mysql-5.1.40-solaris10-sparc-test/mysql-test/var-n_mix/7/log/rpl.rpl_auto_increment-InnoDB plugin/' to '/export/home/pb2/test/sb_0-810910-1255113498.34/mysql-5.1.40-solaris10-sparc-test/mysql-test/var-n_mix/log/rpl.rpl_auto_increment-InnoDB plugin/' Retrying test, attempt(2/3)... =============== NOTE This result reject relates to a part of the test case where a 'show create table' is issued. A wild guess would be that some problem occurred when loading the innodb plugin (in the slave) and the engine defaulted to myisam, causing: show create table to output different engine. How to repeat: Failure: http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=2377353 Push: http://pb2.norway.sun.com/web.py?template=push_details&push=571069