Bug #19109 | CREATE TABLE on NDB is not propagated to a SQL node if the node is down | ||
---|---|---|---|
Submitted: | 14 Apr 2006 22:37 | Modified: | 18 Apr 2006 16:26 |
Reporter: | Ivan Zoratti | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | 5.1.7 | OS: | Linux (Linux RH EL 4) |
Assigned to: | CPU Architecture: | Any |
[14 Apr 2006 22:37]
Ivan Zoratti
[15 Apr 2006 1:24]
Hartmut Holzgraefe
This sounds more as if the api node was not able to connect to the cluster at all, have you checked with ndb_mgm that it was actually connected?
[17 Apr 2006 10:56]
Jonathan Miller
Actually you do not need to restart the cluster to have the down MySQLD (S2) discover the new database. So on the MySQLD (S1) that is up you create database MyStuff with tables t1, and t2. Once you bring up S2 you need to do the following. 1) CREATE DATABASE MyStuff; on the S2 process 2) SHOW TABLES; boom! S2 now knows all about MyStuff database. Thanks!
[17 Apr 2006 23:39]
Jon Stephens
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.mysql.com/documentation/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Additional info: This is already documented in http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-limitations.html: "...autodiscovery of tables is supported... ...after a database named db_name is created or imported using one MySQL server, you should issue a CREATE DATABASE db_name statement on each additional MySQL server that accesses the same MySQL Cluster. ... Once this has been done for a given MySQL server, that server should be able to detect the database tables without error."