Bug #76821 | WatchDog detects no progress in send thread and kills datanode | ||
---|---|---|---|
Submitted: | 24 Apr 2015 10:36 | Modified: | 15 May 2015 9:04 |
Reporter: | Ole John Aske | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | 7.2.21 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[24 Apr 2015 10:36]
Ole John Aske
[27 Apr 2015 7:30]
Ole John Aske
Posted by developer: Note to doc: This issue was already fixed in 7.4 and *backported* to 7.2-> by this fix
[15 May 2015 9:04]
Jon Stephens
Documented fix in the NDB 7.2.21, 7.3.10, 7.4.7, and 7.5.0 changelogs, as follows: Previously, multiple send threads could be invoked for handling sends to the same node; these threads then competed for the same send lock. While the send lock blocked the additional send threads, work threads could be passed to other nodes. This issue is fixed by ensuring that new send threads are not activated while there is already an active send thread assigned to the same node. In addition, a node already having an active send thread assigned to it is no longer visible to other, already active, send threads; that is, such a node is longer added to the node list when a send thread is currently assigned to it. Closed.