| 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: | |
| 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 | ||
[17 Mar 2010 19:09]
Andrew Hutchings
[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.
