| Bug #21535 | 3r: The failure handling of node 1 ends up in an infinite loop. | ||
|---|---|---|---|
| Submitted: | 9 Aug 2006 10:58 | Modified: | 2 Nov 2006 8:38 |
| Reporter: | Lars Torstensson | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
| Version: | MySQL cluster 5.0.22 | OS: | Linux (Redhat Linux 2.6.9-34.ELsmp #1 ) |
| Assigned to: | Jonas Oreland | CPU Architecture: | Any |
[9 Aug 2006 10:58]
Lars Torstensson
[9 Aug 2006 10:58]
Lars Torstensson
Category
[9 Aug 2006 11:19]
Lars Torstensson
I have uploaded (ftp) core and trace files. "bug-data-21535.tar.gz"
[15 Aug 2006 6:59]
Jonas Oreland
see also bug#21481
[15 Aug 2006 7:01]
Jonas Oreland
During fragment distkey is only updated on primary replica + starting replica during node recovery. This leads to that backup 2 (and 3) can get very scewed dist-key, which will be a big problem(crash) if they become primary (due to node failure/shutdown)
[14 Sep 2006 13:37]
Jonas Oreland
Will impl. fix But reported case with master node failure during node recovery as separate bug (and 3 replica) http://bugs.mysql.com/22346
[14 Sep 2006 20:01]
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/11969 ChangeSet@1.2247, 2006-09-14 22:01:26+02:00, jonas@perch.ndb.mysql.com +8 -0 ndb - bug#21535 send new fragdistkeys to all replicas during node recovery to make sure that not 3rd or 4th replicas fragDistKey becomes out of sync
[14 Sep 2006 20:05]
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/11970 ChangeSet@1.2248, 2006-09-14 22:05:35+02:00, jonas@perch.ndb.mysql.com +1 -0 ndb - bug#21535 remove accidently left debug code
[15 Sep 2006 9:18]
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/11998 ChangeSet@1.2249, 2006-09-15 11:18:17+02:00, jonas@perch.ndb.mysql.com +1 -0 ndb - bug#21535 review, Fix also master being "old" version
[10 Oct 2006 18:38]
Jonas Oreland
pushed into 5.1.12
[27 Oct 2006 7:47]
Lars Torstensson
I have managed to reproduce this bug in a 5.0.27 release built from the bk://mysql.bkbits.net/mysql-5.0-ndb repo 2006-10-26 I have a 2 replica 4 node cluster. Reproduce: kill -9 on ndbd node 1 I have uploaded the core/trace/cluster log. BK ChangeLog: ~/mysql-5.0_s3$ grep 21535 -A 5 -B 1 BK/ChangeLog 2006/09/15 11:18:17+02:00 jonas@perch.ndb.mysql.com ndb - bug#21535 review, Fix also master being "old" version ndb/src/kernel/blocks/dblqh/DblqhMain.cpp 2006/09/15 11:18:15+02:00 jonas@perch.ndb.mysql.com +22 -17 Fix also master being "old" version -- 2006/09/14 22:05:35+02:00 jonas@perch.ndb.mysql.com ndb - bug#21535 remove accidently left debug code ndb/src/kernel/blocks/dblqh/DblqhMain.cpp 2006/09/14 22:05:34+02:00 jonas@perch.ndb.mysql.com +0 -11 remove accidently left debug code -- 2006/09/14 22:01:26+02:00 jonas@perch.ndb.mysql.com ndb - bug#21535 send new fragdistkeys to all replicas during node recovery to make sure that not 3rd or 4th replicas fragDistKey becomes out of sync ndb/include/kernel/GlobalSignalNumbers.h 2006/09/14 22:01:24+02:00 jonas@perch.ndb.mysql.com +1 -0
[27 Oct 2006 7:50]
Lars Torstensson
File name bug-21535-2006-10-26.tar.gz
[1 Nov 2006 14:43]
Jonas Oreland
pushed into 5.0.29
[2 Nov 2006 8:38]
Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.
If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at
http://dev.mysql.com/doc/en/installing-source.html
Documented bugfix for 5.0.29 & 5.1.12.
[4 Nov 2006 3:22]
Jon Stephens
*Fix for 5.0 documented in 5.0.30 Release Notes.*
