MySQL Bugs: #39612: Database discovery works only when the mysqld is connected to the cluster.

Bug #39612	Database discovery works only when the mysqld is connected to the cluster.
Submitted:	23 Sep 2008 18:37	Modified:	4 Oct 2008 8:16
Reporter:	Bogdan Kecman	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.1+	OS:	Any
Assigned to:	Tomas Ulin	CPU Architecture:	Any

Description:
Database discovery works only when the mysqld is connected to the cluster. 

If SQL node was not connected, and rejoins, the database need to be created manually.

How to repeat:
Start data nodes
Start all but one SQL node
Create DB xyz
Start remaining SQL node -> node does not see DB xyz

Suggested fix:
Document this as part of the Limitations with Multiple Nodes.

This is already documented. 

From http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-limitations-resolved.html:

    Autodiscovery of databases is now supported for multiple MySQL servers 
    accessing the same MySQL Cluster, **provided that a given mysqld is already 
    running and is connected to the cluster at the time that the database is 
    created on a different mysqld**.

    What this means is that if a mysqld process first connects to the cluster 
    after a database named db_name has been created, you should issue a CREATE 
    SCHEMA db_name statement on the “new” MySQL server when it first accesses 
    that MySQL Cluster. Once this has been done, the “new” mysqld should be 
    able to detect any tables in that database tables without errors.

fixed in 6.2.16 and 6.3.18

Documented 2008-10-03 in the 6.3.18 changelog and elsewhere in the 5.1 Manual as appropriate. See http://lists.mysql.com/commits/55272 for details.

Fix now also documented for NDB-6.2.16 - http://lists.mysql.com/commits/55304