Bug #21383 Bug in error handling of scan leads to node crash later on
Submitted: 1 Aug 2006 8:46 Modified: 2 Aug 2006 14:19
Reporter: Jonas Oreland Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.0.22 OS:
Assigned to: Jonas Oreland CPU Architecture:Any

[1 Aug 2006 8:46] Jonas Oreland
Description:
A SCAN_TABREQ readcommitted (with following ATTRINFO) leads to _no_ action
  in signal log, likely an error case (jam wasnt long enought to see)

However some incorrect state is set as the following SCAN_TABREQ leads to node
  crash

How to repeat:
 

Suggested fix:
[2 Aug 2006 14:19] Jonas Oreland
Hi,

I wrote a test program specificly to try to reproduce this problems..
Wo/ luck...therefore closing as "Cant repeat" until I get similar issue with logs files preserved.