svn commit - mysqldoc@docsrva: r11972 - in trunk: dynamic-docs/changelog refman-5.1

[jon]

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 @@
 ]>
 <changelog>
 
+  <logentry entrytype="feature">
+
+    <tags>
+      <highlight type="cluster"/>
+      <manual type="autodiscovery"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="39612"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.28-ndb-6.3.18"/>
+    </versions>
+
+    <message>
+
+      <para>
+        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 <literal>CREATE DATABASE</literal> (or
+        <literal>CREATE SCHEMA</literal>) 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
+        <literal>NDCLUSTER</literal> tables that it contains.
+      </para>
+
+    </message>
+
+  </logentry>
+
   <logentry entrytype="bug">
 
     <tags>


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 @@
 
             <para>
               Autodiscovery of databases is now supported for multiple
-              MySQL servers accessing the same MySQL Cluster, provided
-              that a given <command>mysqld</command> is already running
-              and is connected to the cluster at the time that the
-              database is created on a different
-              <command>mysqld</command>.
+              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
+              <command>mysqld</command> was already running and
+              connected to the cluster at the time that the database was
+              created on a different <command>mysqld</command> &mdash;
+              in other words, when a <command>mysqld</command> process
+              connected to the cluster after a database named
+              <replaceable>db_name</replaceable> was created, it was
+              necessary to issue a <literal>CREATE DATABASE
+              <replaceable>db_name</replaceable></literal> or
+              <literal>CREATE SCHEMA
+              <replaceable>db_name</replaceable></literal> statement on
+              the <quote>new</quote> MySQL server when it first
+              accesseed that MySQL Cluster. Beginning with MySQL Cluster
+              NDB 6.3.18, such a <literal>CREATE</literal> statement is
+              no longer required. (Bug #39612)
             </para>
 
           </formalpara>
 
           <para>
-            What this means is that if a <command>mysqld</command>
-            process first connects to the cluster after a database named
-            <replaceable>db_name</replaceable> has been created, you
-            should issue a <literal>CREATE SCHEMA
-            <replaceable>db_name</replaceable></literal> statement on
-            the <quote>new</quote> MySQL server when it first accesses
-            that MySQL Cluster. Once this has been done, the
-            <quote>new</quote> <command>mysqld</command> should
be able
-            to detect any tables in that database tables without errors.
-          </para>
-
-          <para>
             This also means that online schema changes in
             <literal>NDB</literal> tables are now possible. That is, the
             result of operations such as <literal>ALTER TABLE</literal>


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 @@
           </formalpara>
         </listitem>
 
+        <listitem>
+          <formalpara>
+
+            <title>Fully automatic database discovery</title>
+
+            <para>
+              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 <literal>CREATE DATABASE</literal> or
+              <literal>CREATE SCHEMA</literal> statement to be issued on
+              the new SQL node after it joins the cluster.
+            </para>
+
+          </formalpara>
+        </listitem>
+
       </itemizedlist>
     </para>