Bug #39613 SQL node freeze after DB dropped then recreated from another SQL node
Submitted: 23 Sep 2008 20:49 Modified: 4 Oct 2008 10:43
Reporter: Bogdan Kecman
Status: Closed
Category:Server: Cluster Severity:S3 (Non-critical)
Version:mysql-5.1.24 ndb-6.3.16, 6.3.15 OS:Any
Assigned to: Target Version:

[23 Sep 2008 20:49] Bogdan Kecman 
Description:
SQL node stuck after DB dropped then recreated from another SQL node

How to repeat:
start cluster
 - 2 data nodes
 - 1 mgm node
 - 2 sql nodes

login to sql node1 drop DB x; create DB x;
sql node2 will be "stuck"

Suggested fix:
this might be the part of "db discovery limitation" but even if this is a "limitation" -
it should not freeze mysqld
[3 Oct 2008 16:07] Tomas Ulin 
fixed in 6.2.16 and 6.3.18
[4 Oct 2008 10:43] Jon Stephens 
Documented fix in the NDB 6.2.16 and NDB 6.3.18 changelogs as follows:

        Dropping and then re-creating a database on one SQL node caused other
        SQL nodes to hang.