Author: jstephens
Date: 2006-10-17 17:54:50 +0200 (Tue, 17 Oct 2006)
New Revision: 3663
Log:
Fixed outdated references regarding autodiscovery/table schema changes.
(Thanks for the reminder, Roland!)
Modified:
trunk/refman-5.1/mysql-cluster.xml
Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml 2006-10-17 11:20:56 UTC (rev 3662)
+++ trunk/refman-5.1/mysql-cluster.xml 2006-10-17 15:54:50 UTC (rev 3663)
Changed blocks: 7, Lines Added: 23, Lines Deleted: 63; 5691 bytes
@@ -1834,10 +1834,7 @@
databases. (See <xref linkend="mysql-cluster-limitations"/>.)
This means that, once the <literal>world</literal> database and
its tables have been created on one data node, you need to issue
- the <literal>CREATE SCHEMA world</literal> statement, followed
- by <literal>FLUSH TABLES</literal> on each SQL node in the
- cluster. This causes the node to recognize the database and read
- its table definitions.
+ the <literal>CREATE SCHEMA world</literal> statement.
</para>
<para>
@@ -16217,8 +16214,15 @@
<literal>apply_status</literal> table.
</para>
</listitem>
-
+
+<!--
<listitem>
+ <remark>
+ [js] This does not seem to be necessary any longer in 5.1,
+ since table schema changes are now detected by all SQL
+ nodes.
+ </remark>
+
<para>
Next, it is necessary to make all nodes in the slave cluster
aware of the new tables. (This is due to the fact that the
@@ -16243,7 +16247,7 @@
host acting as a data node in the slave cluster.
</para>
</listitem>
-
+-->
<listitem>
<para>
Now you need to obtain the most recent epoch from the
@@ -16699,39 +16703,6 @@
</orderedlist>
- <para>
- Note that when you create a new <literal>NDB Cluster</literal>
- table on the master cluster, if you do so using the
- <command>mysqld</command> that acts as the replication master,
- you must execute a <literal>SHOW TABLES</literal>, also on the
- master <command>mysqld</command>, to initiate discovery
- properly. Otherwise, the new table and any data it contains
- cannot be seen by the replication master
- <command>mysqld</command>, nor by the slave (that is, neither
- the new table nor its data is replicated). If the table is
- created on a <command>mysqld</command> that is not acting as
- the replication master, it does not matter which
- <command>mysqld</command> issues the <literal>SHOW
- TABLES</literal>.
- </para>
-
- <para>
- It is also possible to force discovery by issuing a
- <quote>dummy</quote> <literal>SELECT</literal> statement using
- the new or altered table in the statement's
- <literal>FROM</literal> clause. Although the statement fails,
- it causes the change to be recognized by the cluster. However,
- issuing a <literal>SHOW TABLES</literal> is the preferred
- method.
- </para>
-
- <para>
- We are working to implement automatic discovery of schema
- changes in a future MySQL Cluster release. For more
- information about this and other Cluster issues, see
- <xref linkend="mysql-cluster-limitations"/>.
- </para>
-
</section>
</section>
@@ -18961,22 +18932,6 @@
<listitem>
<para>
- It is not possible to make online schema changes such as
- those accomplished using <literal>ALTER TABLE</literal> or
- <literal>CREATE INDEX</literal>, as the <literal>NDB
- Cluster</literal> engine does not support autodiscovery of
- such changes. (However, you can import or create a table
- that uses a different storage engine, and then convert it
- to <literal>NDB</literal> using <literal>ALTER TABLE
- <replaceable>tbl_name</replaceable>
- ENGINE=NDBCLUSTER</literal>. In such a case, you must
- issue a <literal>FLUSH TABLES</literal> statement to force
- the cluster to pick up the change.)
- </para>
- </listitem>
-
- <listitem>
- <para>
Online adding or dropping of nodes is not possible (the
cluster must be restarted in such cases).
</para>
@@ -19170,12 +19125,7 @@
database is created on a different
<command>mysqld</command>.
</para>
-
- <remark role="todo">
- [js] Update references to autodiscovery to reflect this
- change!
- </remark>
-
+
<para>
What this means is that if a <command>mysqld</command>
process first connects to the cluster after a database
@@ -19185,9 +19135,19 @@
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 the any tables in that database tables
- without error.
+ 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> and <literal>CREATE INDEX</literal>
+ performed on one SQL node in the cluster are now visible
+ to the cluster's other SQL nodes without any additional
+ action being taken.
+ </para>
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3663 - trunk/refman-5.1 | jon | 17 Oct |
