Bug #35148 | Error '4009 Cluster Failure' in various tests on various platforms | ||
---|---|---|---|
Submitted: | 7 Mar 2008 16:15 | Modified: | 6 Jul 2009 11:49 |
Reporter: | Joerg Bruehe | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | mysql-5.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | 5.0.58 |
[7 Mar 2008 16:15]
Joerg Bruehe
[23 May 2008 14:06]
Joerg Bruehe
Bug also occurs in the 5.0.62 release build. Affected tests with identical symptoms to those already classified here (most likely, from 5.0.58) are loaddata_autocom_ndb ndb_alter_table ndb_autodiscover3 ndb_autodiscover ndb_basic ndb_bitfield ndb_cache ps_7ndb strict_autoinc_5ndb
[6 Jul 2009 9:03]
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/77988 2793 Georgi Kodinov 2009-07-06 Bug#38315 and Bug#35148: disabled sporadically failing NDB tests
[6 Jul 2009 9:04]
Georgi Kodinov
moving back to verified. Just a test case disablement
[6 Jul 2009 10:24]
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/78003 2796 Georgi Kodinov 2009-07-06 Bug #35148: disabled testcase loaddata_autocom_ndb
[6 Jul 2009 10:28]
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/78004 2797 Georgi Kodinov 2009-07-06 Bug #35148: ndb_autodiscover3 disabled
[6 Jul 2009 11:49]
Georgi Kodinov
back to verified : test case disablement.
[7 Jul 2009 7:52]
Bugs System
Pushed into 5.0.84 (revid:joro@sun.com-20090707074938-ksah1ibn0vs92cem) (version source revid:joro@sun.com-20090706102719-2g256ax0ndg9jrlh) (merge vers: 5.0.84) (pib:11)
[8 Jul 2009 13:30]
Bugs System
Pushed into 5.1.37 (revid:joro@sun.com-20090708131116-kyz8iotbum8w9yic) (version source revid:joro@sun.com-20090706103609-62l08z5dpwqy29wt) (merge vers: 5.1.37) (pib:11)
[9 Jul 2009 7:35]
Bugs System
Pushed into 5.0.84 (revid:joro@sun.com-20090707074938-ksah1ibn0vs92cem) (version source revid:joro@sun.com-20090706102719-2g256ax0ndg9jrlh) (merge vers: 5.0.84) (pib:11)
[9 Jul 2009 7:37]
Bugs System
Pushed into 5.1.37 (revid:joro@sun.com-20090708131116-kyz8iotbum8w9yic) (version source revid:joro@sun.com-20090706103609-62l08z5dpwqy29wt) (merge vers: 5.1.37) (pib:11)
[10 Jul 2009 11:20]
Bugs System
Pushed into 5.4.4-alpha (revid:anozdrin@bk-internal.mysql.com-20090710111017-bnh2cau84ug1hvei) (version source revid:joro@sun.com-20090706104514-4dj1xron15x44x6h) (merge vers: 5.4.4-alpha) (pib:11)
[26 Aug 2009 13:46]
Bugs System
Pushed into 5.1.37-ndb-7.0.8 (revid:jonas@mysql.com-20090826132541-yablppc59e3yb54l) (version source revid:jonas@mysql.com-20090826132541-yablppc59e3yb54l) (merge vers: 5.1.37-ndb-7.0.8) (pib:11)
[26 Aug 2009 13:46]
Bugs System
Pushed into 5.1.37-ndb-6.3.27 (revid:jonas@mysql.com-20090826105955-bkj027t47gfbamnc) (version source revid:jonas@mysql.com-20090826105955-bkj027t47gfbamnc) (merge vers: 5.1.37-ndb-6.3.27) (pib:11)
[26 Aug 2009 13:48]
Bugs System
Pushed into 5.1.37-ndb-6.2.19 (revid:jonas@mysql.com-20090825194404-37rtosk049t9koc4) (version source revid:jonas@mysql.com-20090825194404-37rtosk049t9koc4) (merge vers: 5.1.37-ndb-6.2.19) (pib:11)
[27 Aug 2009 16:32]
Bugs System
Pushed into 5.1.35-ndb-7.1.0 (revid:magnus.blaudd@sun.com-20090827163030-6o3kk6r2oua159hr) (version source revid:jonas@mysql.com-20090826132541-yablppc59e3yb54l) (merge vers: 5.1.37-ndb-7.0.8) (pib:11)
[26 Jul 2010 12:19]
Sven Sandberg
I have seen this a few times recently when running the entire suite on my machine. E.g.: rpl_ndb.rpl_ndb_circular_2ch [ pass ] 22837 MTR's internal check of the test case 'rpl_ndb.rpl_ndb_circular_2ch' failed. This means that the test case does not preserve the state that existed before the test case was executed. Most likely the test case did not do a proper clean-up. This is the diff of the states of the servers before and after the test case was executed: mysqltest: Logging to '/home/sven/bzr/b49978-cleanup_rpl_tests/5.1-bugteam/mysql-test/var/tmp/check-mysqld_1_1.log'. mysqltest: Results saved in '/home/sven/bzr/b49978-cleanup_rpl_tests/5.1-bugteam/mysql-test/var/tmp/check-mysqld_1_1.result'. mysqltest: Connecting to server localhost:12603 (socket /home/sven/bzr/b49978-cleanup_rpl_tests/5.1-bugteam/mysql-test/var/tmp/mysqld.1.1.sock) as 'root', connection 'default', attempt 0 ... mysqltest: ... Connected. mysqltest: Start processing test commands from './include/check-testcase.test' ... mysqltest: ... Done processing test commands. --- /home/sven/bzr/b49978-cleanup_rpl_tests/5.1-bugteam/mysql-test/var/tmp/check-mysqld_1_1.result 2010-07-26 14:41:43.000000000 +0300 +++ /home/sven/bzr/b49978-cleanup_rpl_tests/5.1-bugteam/mysql-test/var/tmp/check-mysqld_1_1.reject 2010-07-26 14:42:07.000000000 +0300 @@ -513,7 +513,3 @@ mysql.time_zone_transition 3895294076 mysql.time_zone_transition_type 168184411 mysql.user 3850358533 -Warnings: -Error 1296 Got error 4009 'Cluster Failure' from NDB -Error 1296 Got error 4009 'Cluster Failure' from NDB -Error 1296 Got error 4009 'Cluster Failure' from NDB mysqltest: Result length mismatch not ok