Bug #10029 crash in ordered index scan after db full
Submitted: 20 Apr 2005 13:02 Modified: 4 May 2005 15:03
Reporter: Pekka Nousiainen Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:4.1.11 OS:
Assigned to: Pekka Nousiainen CPU Architecture:Any

[20 Apr 2005 13:02] Pekka Nousiainen
Two index scans crash on replicates due to invalid tuple version.
Db was 100% full (failed ops possible cause of corruption).

Date/Time: Wednesday 20 April 2005 - 09:05:22
Problem data: DbtupIndex.cpp
Object of reference: DBTUP (Line: 136) 0x0000000a

Date/Time: Wednesday 20 April 2005 - 09:06:55
Problem data: DbtupExecQuery.cpp
Object of reference: DBTUP (Line: 398) 0x0000000a

How to repeat:
not yet
[21 Apr 2005 15:47] Pekka Nousiainen
Easily verified.

Another bug with same symptom was fixed in:
ChangeSet@1.2055.182.1, 2004-12-03 15:00:56+01:00
[23 Apr 2005 15:49] 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: