From: Date: October 3 2008 4:44pm Subject: svn commit - mysqldoc@docsrva: r11972 - in trunk: dynamic-docs/changelog refman-5.1 List-Archive: http://lists.mysql.com/commits/55272 Message-Id: <200810031444.m93EipGn021241@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: jstephens Date: 2008-10-03 16:44:51 +0200 (Fri, 03 Oct 2008) New Revision: 11972 Log: Documenting fix for Cluster Bug #39612 (fully functional autodiscovery) Modified: trunk/dynamic-docs/changelog/mysqld-1.xml trunk/refman-5.1/mysql-cluster-limitations.xml trunk/refman-5.1/mysql-cluster-roadmap.xml Modified: trunk/dynamic-docs/changelog/mysqld-1.xml =================================================================== --- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-10-03 13:52:14 UTC (rev 11971) +++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-10-03 14:44:51 UTC (rev 11972) Changed blocks: 1, Lines Added: 32, Lines Deleted: 0; 1210 bytes @@ -6,6 +6,38 @@ ]> + + + + + + + + + + + + + + + + + + + It is no longer a requirement for database autodiscovery that an + SQL node already be connected to the cluster at the time that a + database is created on another SQL node. It is no longer + necessary to issue CREATE DATABASE (or + CREATE SCHEMA) statements on an SQL node + joining the cluster after a database is created in order for the + new SQL node to see the database and any + NDCLUSTER tables that it contains. + + + + + + Modified: trunk/refman-5.1/mysql-cluster-limitations.xml =================================================================== --- trunk/refman-5.1/mysql-cluster-limitations.xml 2008-10-03 13:52:14 UTC (rev 11971) +++ trunk/refman-5.1/mysql-cluster-limitations.xml 2008-10-03 14:44:51 UTC (rev 11972) Changed blocks: 1, Lines Added: 17, Lines Deleted: 17; 2706 bytes @@ -1678,28 +1678,28 @@ 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. + MySQL servers accessing the same MySQL Cluster. Formerly, + autodiscovery in MySQL Cluster 5.1 and MySQL Cluster NDB + 6.x releases required that a given + mysqld was already running and + connected to the cluster at the time that the database was + created on a different mysqld — + in other words, when a mysqld process + connected to the cluster after a database named + db_name was created, it was + necessary to issue a CREATE DATABASE + db_name or + CREATE SCHEMA + db_name statement on + the new MySQL server when it first + accesseed that MySQL Cluster. Beginning with MySQL Cluster + NDB 6.3.18, such a CREATE statement is + no longer required. (Bug #39612) - 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. - - - This also means that online schema changes in NDB tables are now possible. That is, the result of operations such as ALTER TABLE Modified: trunk/refman-5.1/mysql-cluster-roadmap.xml =================================================================== --- trunk/refman-5.1/mysql-cluster-roadmap.xml 2008-10-03 13:52:14 UTC (rev 11971) +++ trunk/refman-5.1/mysql-cluster-roadmap.xml 2008-10-03 14:44:51 UTC (rev 11972) Changed blocks: 1, Lines Added: 17, Lines Deleted: 0; 981 bytes @@ -1259,6 +1259,23 @@ + + + + Fully automatic database discovery + + + It is no longer a requirement for database autodiscovery + that an SQL node already be connected to the cluster at + the time that a database is created on another SQL node, + or for a CREATE DATABASE or + CREATE SCHEMA statement to be issued on + the new SQL node after it joins the cluster. + + + + +