Bug #52156 Incomplete log message shows wrong log group
Submitted: 17 Mar 2010 19:09 Modified: 24 May 2010 14:00
Reporter: Andrew Hutchings Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.3 OS:Any
Assigned to: CPU Architecture:Any
Tags: mysql-5.1.37-ndb-6.3.27a
Triage: Triaged: D4 (Minor) / R2 (Low) / E6 (Needs Assessment)

[17 Mar 2010 19:09] Andrew Hutchings
Description:
We are seeing the message:

2010-03-15 15:08:39 [ndbd] INFO -- Incomplete log for node group: 1! starting nodes: 0000000000001ff0

When in fact it is node group 0 with the incomplete log.

How to repeat:
.
[17 Mar 2010 19:17] Andrew Hutchings
I suspect the cause is in Dbdih::execDIH_RESTARTREQ

for (i++ ; i<MAX_NDB_NODES; i++)
{
...
signal->theData[0] = i;
...
}

So the node group in the signal data returned will always be > 0.