Bug #48697 | Accounting of scan records is incorrect causing node failure | ||
---|---|---|---|
Submitted: | 11 Nov 2009 19:54 | Modified: | 15 Nov 2009 20:45 |
Reporter: | Andrew Hutchings | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | OS: | Any | |
Assigned to: | Jonas Oreland | CPU Architecture: | Any |
[11 Nov 2009 19:54]
Andrew Hutchings
[12 Nov 2009 13: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/90235 3167 Jonas Oreland 2009-11-12 ndb - bug#48697 - fix accounting of scans in LQH (wrt to reserved for LCP/NR)
[12 Nov 2009 13:20]
Jonas Oreland
pushed to 6.3.29 and 7.0.10 docs: accounting of no of free scan records in LQH could get "out-of-sync"/corrupted/screwed-up... so that node-recovery (or LCP) could find it self without a scan-record...causing node to crash
[15 Nov 2009 20:45]
Jon Stephens
Documented bugfix in the NDB-6.3.29 and 7.0.10 changelogs as follows: Under certain conditions, accounting of the number of free scan records in the local query handler could be incorrect, so that during node recovery or a local checkpoint operations, the LQH could find itself lacking a scan record that is expected to find, causing the node to crash. Closed.