Bug #6327 CREATE TABLE showing irrelevant NDB warnings
Submitted: 29 Oct 2004 16:10 Modified: 3 Dec 2004 6:02
Reporter: Dean Ellis Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.8 OS:
Assigned to: Assigned Account CPU Architecture:Any

[29 Oct 2004 16:10] Dean Ellis
Description:
When NDB is enabled, but the NDB cluster itself is down, CREATE TABLE statements for non-NDB storage engines produce warnings about NDB.

How to repeat:
Enable NDB support; start mysqld without starting NDB cluster.

CREATE TABLE t1 ( a int ) ENGINE=MyISAM;
SHOW WARNINGS;

ie:

mysql> show warnings;
+-------+------+-------------------------------------------+
| Level | Code | Message                                   |
+-------+------+-------------------------------------------+
| Error | 1296 | Got error 4009 'Cluster Failure' from NDB |
+-------+------+-------------------------------------------+
[29 Oct 2004 16:49] Dean Ellis
The server needs to check to see if the table already exists in the cluster, so I assume that is the source of the warning.  However, should the CREATE TABLE be allowed to continue if it cannot contact the cluster?
[3 Nov 2004 6:02] Jonas Oreland
We have discussed that back and forth, and concluded
that it's ok.

For later releases (maybe 5.0), we discussed to have a database
 associated with ndb, then no tables would be allowed to be created
 in that database...(but this was only a discussion.)
[14 Feb 2005 22:54] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".