Bug #62208 Api failure handling taking too long can lead to node-crash
Submitted: 19 Aug 2011 8:07 Modified: 19 Aug 2011 16:24
Reporter: Jonas Oreland Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Jonas Oreland CPU Architecture:Any

[19 Aug 2011 8:07] Jonas Oreland 
Description:
When failure handling of a node takes longer than 60s
extra debug output is emitted.

However, these extra debug, could cause crash, as it tried to
printout data-node information even for api-nodes.

This yields a crash if api-node id > 48,
and confusing output if api-node id <= 48

How to repeat:
.

Suggested fix:
.
[19 Aug 2011 8:09] Jonas Oreland 
correction, it should be longer than 300s i.e 5 minutes
[19 Aug 2011 8:25] Jonas Oreland 
pushed to 6.3.46, 7.0.27 and 7.1.16
[19 Aug 2011 8:26] Jonas Oreland 
Patch for 7.1.11

Attachment: bug62208.711.patch (application/octet-stream, text), 1.43 KiB.
[19 Aug 2011 16:24] Jon Stephens 
Documented bugfix in the NDB 6.3.46, 7.0.27, and 7.1.17 changelogs as follows:

        When failure handling of an API node takes longer than 300
        seconds, extra debug information is included in the resulting
        output. In cases where the API node&apos;s node ID was greater
        than 48, these extra debug messages could lead to a crash, and
        confuing output otherwise. This was due to an attempt to provide
        information specific to data nodes for API nodes as well.

Closed.