Bug #59569 Operation hangs indefinitely if running another operation from another client
Submitted: 17 Jan 2011 20:29 Modified: 25 Jan 2011 11:41
Reporter: Andrew Morgan Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Cluster Manager: Agent Severity:S3 (Non-critical)
Version:MCM 1.1.0 OS:Linux (Fedora 13)
Assigned to: CPU Architecture:Any

[17 Jan 2011 20:29] Andrew Morgan
Description:
Running with this Cluster...

mysql> show status -r mycluster;
+------+----------+-------------+---------+-----------+
| Id   | Process  | Host        | Status  | Nodegroup |
+------+----------+-------------+---------+-----------+
| 1    | ndb_mgmd | 192.168.1.8 | running |           |
| 2    | ndbd     | 192.168.1.8 | running | 0         |
| 3    | ndbd     | 192.168.1.9 | running | 0         |
| 4    | mysqld   | 192.168.1.8 | running |           |
| 5    | mysqld   | 192.168.1.9 | running |           |
+------+----------+-------------+---------+-----------+
5 rows in set (0.89 sec)

... from one client connected to 192.168.1.8 I initiated the shutdown of node 2; from a second client connected to 192.168.1.9 I then issued a command to shutdown node 4 (without waiting for the first command to complete. The second command completed and then I started node 4 again. The original command did not return (though node 2 had stopped). I had to kill the client.

How to repeat:
Follow the steps above

Suggested fix:
Either prevent multiple status-changing commands being run at once or make sure that all commands return.
[18 Jan 2011 9:30] Kari Juul Wedde
Probably a duplicate of 49698