| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | March 9 2007 1:53pm |
| Subject: | svn commit - mysqldoc@docsrva: r5276 - branches/telcos/refman-5.1 trunk/refman-4.1 trunk/refman-5.0 trunk/refman-5.1 | ||
| View as plain text | |||
Author: jstephens Date: 2007-03-09 13:53:52 +0100 (Fri, 09 Mar 2007) New Revision: 5276 Log: Reformat. Modified: branches/telcos/refman-5.1/mysql-cluster.xml trunk/refman-4.1/mysql-cluster.xml trunk/refman-5.0/mysql-cluster.xml trunk/refman-5.1/mysql-cluster.xml Modified: branches/telcos/refman-5.1/mysql-cluster.xml =================================================================== --- branches/telcos/refman-5.1/mysql-cluster.xml 2007-03-09 12:52:29 UTC (rev 5275) +++ branches/telcos/refman-5.1/mysql-cluster.xml 2007-03-09 12:53:52 UTC (rev 5276) Changed blocks: 12, Lines Added: 66, Lines Deleted: 65; 10882 bytes @@ -2957,7 +2957,7 @@ set it on the command line or in the <filename>my.cnf</filename> file for each executable. </para> - + <para> The maximum length of a connectstring is 1024 characters. </para> @@ -12350,80 +12350,82 @@ </itemizedlist> </section> - + <section id="mysql-cluster-sql-statements"> + <title>Quick Reference: MySQL Cluster SQL Statements</title> - + <indexterm> <primary>MySQL Cluster</primary> <secondary>SQL statements for monitoring</secondary> </indexterm> - + <indexterm> <primary>SQL statements relating to MySQL Cluster</primary> </indexterm> - + <para> This section discusses several SQL statements that can prove useful in managing and monitoring a MySQL server that is connected to a MySQL Cluster, and in some cases provide - information about the cluster itself. + information about the cluster itself. </para> - + <itemizedlist> + <listitem> <indexterm> <primary>SHOW ENGINE</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <indexterm> <primary>SHOW ENGINE NDB STATUS</primary> </indexterm> - + <indexterm> <primary>SHOW ENGINE NDBCLUSTER STATUS</primary> </indexterm> - + <para> <literal>SHOW ENGINE NDB STATUS</literal>, <literal>SHOW ENGINE NDBCLUSTER STATUS</literal> </para> - + <para> The output of this statement contains information about the server's connection to the cluster, creation and usage of MySQL Cluster objects, and binary logging for MySQL Cluster replication. </para> - + <para> See <xref linkend="show-engine"/>, for a usage example and more detailed information. </para> </listitem> - + <listitem> <indexterm> <primary>SHOW ENGINES</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <para> <literal>SHOW ENGINES</literal> </para> - + <para> This statement can be used to determine whether or not clustering support is enabled in the MySQL server, and if so, whether it is active. </para> - + <para> See <xref linkend="show-engines"/>, for more detailed information. </para> - + <note> <para> In MySQL 5.1, this statement no longer supports a @@ -12434,18 +12436,18 @@ </para> </note> </listitem> - + <listitem> <indexterm> <primary>INFORMATION_SCHEMA.ENGINES table</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <para> <literal>SELECT * FROM INFORMATION_SCHEMA.ENGINES [WHERE - ENGINE LIKE 'NDB%']</literal> + ENGINE LIKE 'NDB%']</literal> </para> - + <para> This is the equivalent of <literal>SHOW ENGINES</literal>, but uses the <literal>ENGINES</literal> table of the @@ -12458,7 +12460,7 @@ shows whether the server was built with <literal>NDB</literal> support and, if so, whether it is enabled: - + <programlisting> mysql> <userinput>SELECT SUPPORT FROM INFORMATION_SCHEMA.ENGINES</userinput> -> <userinput>WHERE ENGINE LIKE 'NDB%';</userinput> @@ -12467,29 +12469,29 @@ +---------+ | ENABLED | +---------+ -</programlisting> +</programlisting> </para> - + <para> See <xref linkend="engines-table"/>, for more information. </para> </listitem> - + <listitem> <indexterm> <primary>SHOW VARIABLES</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <para> <literal>SHOW VARIABLES LIKE 'NDB%'</literal> </para> - + <para> This statement provides a list of most server system variables relating to the <literal>NDB</literal> storage engine, and their values, as shown here: - + <programlisting> mysql> <userinput>SHOW VARIABLES LIKE 'NDB%';</userinput> +-------------------------------------+-------+ @@ -12510,29 +12512,29 @@ +-------------------------------------+-------+ </programlisting> </para> - + <para> See <xref linkend="server-system-variables"/>, for more information. </para> </listitem> - + <listitem> <indexterm> <primary>INFORMATION_SCHEMA.GLOBAL_VARIABLES table</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <para> <literal>SELECT * FROM INFORMATION_SCHEMA.GLOBAL_VARIABLES - WHERE VARIABLE_NAME LIKE 'NDB%';</literal> + WHERE VARIABLE_NAME LIKE 'NDB%';</literal> </para> - + <para> This statement is the equivalent of the <literal>SHOW</literal> described in the previous item, and provides almost identical output, as shown here: - + <programlisting> mysql> <userinput>SELECT * FROM INFORMATION_SCHEMA.GLOBAL_VARIABLES</userinput> -> <userinput>WHERE VARIABLE_NAME LIKE 'NDB%';</userinput> @@ -12553,10 +12555,10 @@ | NDB_USE_TRANSACTIONS | ON | +-------------------------------------+----------------+ </programlisting> - + Unlike the case with the <literal>SHOW</literal> statement, it is possible to select individual columns. For example: - + <programlisting> mysql> <userinput>SELECT VARIABLE_VALUE </userinput> -> <userinput>FROM INFORMATION_SCHEMA.GLOBAL_VARIABLES</userinput> @@ -12566,26 +12568,26 @@ +----------------+ | ON | +----------------+ -</programlisting> +</programlisting> </para> - + <para> - See <xref linkend="variables-table"/>, and + See <xref linkend="variables-table"/>, and <xref linkend="server-system-variables"/>, for more information. </para> </listitem> - + <listitem> <indexterm> <primary>SHOW STATUS</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <para> <literal>SHOW STATUS LIKE 'NDB%'</literal> </para> - + <para> This statement shows at a glance whether or not the MySQL server is acting as a cluster SQL node, and if so, it @@ -12593,7 +12595,7 @@ and port for the cluster management server to which it is connected, and the number of data nodes in the cluster, as shown here: - + <programlisting> mysql> <userinput>SHOW STATUS LIKE 'NDB%';</userinput> +--------------------------+---------------+ @@ -12604,12 +12606,12 @@ | Ndb_config_from_port | 1186 | | Ndb_number_of_data_nodes | 4 | +--------------------------+---------------+ -</programlisting> - +</programlisting> + If the MySQL server was built with clustering support, but it is not connected to a cluster, all rows in the output of this statement contain a zero or an empty string: - + <programlisting> mysql> <userinput>SHOW STATUS LIKE 'NDB%';</userinput> +--------------------------+-------+ @@ -12620,43 +12622,43 @@ | Ndb_config_from_port | 0 | | Ndb_number_of_data_nodes | 0 | +--------------------------+-------+ -</programlisting> +</programlisting> </para> - + <para> See also <xref linkend="show-status"/>. </para> </listitem> - + <listitem> <indexterm> <primary>INFORMATION_SCHEMA.GLOBAL_STATUS table</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <para> <literal>SELECT * FROM INFORMATION_SCHEMA.GLOBAL_STATUS - WHERE VARIABLE_NAME LIKE 'NDB%';</literal> + WHERE VARIABLE_NAME LIKE 'NDB%';</literal> </para> - + <para> Beginning with MySQL 5.1.12, this statement provides similar output to the <literal>SHOW</literal> statement discussed in the previous item. However, unlike the case with <literal>SHOW STATUS</literal>, it is possible using the <literal>SELECT</literal> to extract values in SQL for use - in scripts for monitoring and automation purposes. + in scripts for monitoring and automation purposes. </para> - + <para> See <xref linkend="status-table"/>, for more information. </para> </listitem> + </itemizedlist> - + </section> - - + </section> <section id="mysql-cluster-backup"> @@ -19777,21 +19779,20 @@ Temporary tables are not supported. </para> </listitem> - + <listitem> <para> You cannot create indexes on <literal>NDB</literal> table columns that use any of the <literal>TEXT</literal> or - <literal>BLOB</literal> data types. + <literal>BLOB</literal> data types. </para> - + <para> - The <literal>NDB</literal> storage - engine also does not support <literal>FULLTEXT</literal> - indexes (these are supported by <literal>MyISAM</literal> - only). + The <literal>NDB</literal> storage engine also does not + support <literal>FULLTEXT</literal> indexes (these are + supported by <literal>MyISAM</literal> only). </para> - + <para> However, you can index <literal>VARCHAR</literal> columns of <literal>NDB</literal> tables. Modified: trunk/refman-4.1/mysql-cluster.xml =================================================================== --- trunk/refman-4.1/mysql-cluster.xml 2007-03-09 12:52:29 UTC (rev 5275) +++ trunk/refman-4.1/mysql-cluster.xml 2007-03-09 12:53:52 UTC (rev 5276) Changed blocks: 11, Lines Added: 63, Lines Deleted: 56; 10276 bytes @@ -870,7 +870,7 @@ <primary>MySQL Cluster</primary> <secondary>and DNS</secondary> </indexterm> - + <para> In the interest of simplicity (and reliability), this How-To uses only numeric IP addresses. However, if DNS resolution is @@ -880,11 +880,11 @@ operating system's equivalent for providing a means to do host lookup if such is available. </para> - + <remark role="NOTE"> [js] Candidate for Troubleshooting Guide? </remark> - + <note> <para> A common problem when trying to use hostnames for Cluster @@ -898,45 +898,45 @@ (including some derivatives such as CentOS and Fedora) places the following entries in these machines' <filename>/etc/hosts</filename> files: - + <programlisting> # ndb1 <filename>/etc/hosts</filename>: 127.0.0.1 ndb1.cluster ndb1 localhost.localdomain localhost </programlisting> - + <programlisting> # ndb2 <filename>/etc/hosts</filename>: 127.0.0.1 ndb2.cluster ndb2 localhost.localdomain localhost </programlisting> - - SuSE Linux (including OpenSuSE) places - these entries in the machines' - <filename>/etc/hosts</filename> files: - + + SuSE Linux (including OpenSuSE) places these entries in the + machines' <filename>/etc/hosts</filename> files: + <programlisting> # ndb1 <filename>/etc/hosts</filename>: 127.0.0.1 localhost 127.0.0.2 ndb1.cluster ndb1 </programlisting> - + <programlisting> # ndb2 <filename>/etc/hosts</filename>: 127.0.0.1 localhost 127.0.0.2 ndb2.cluster ndb2 </programlisting> - + In both instances, <literal>ndb1</literal> routes <literal>ndb1.cluster</literal> to a loopback IP address, but gets a public IP address from DNS for - <literal>ndb2.cluster</literal>, while <literal>ndb2</literal> - routes <literal>ndb2.cluster</literal> to a loopback address - and obtains a public address for + <literal>ndb2.cluster</literal>, while + <literal>ndb2</literal> routes + <literal>ndb2.cluster</literal> to a loopback address and + obtains a public address for <literal>ndb1.cluster</literal>. The result is that each data node connects to the management server, but cannot tell when any other data nodes have connected, and so the data nodes appear to hang while starting. </para> - + <para> You should also be aware that you cannot mix <literal>localhost</literal> and other hostnames or IP @@ -3230,7 +3230,7 @@ set it on the command line or in the <filename>my.cnf</filename> file for each executable. </para> - + <para> The maximum length of a connectstring is 1024 characters. </para> @@ -7485,7 +7485,8 @@ <row> <entry><literal><link linkend="mysql-cluster-param-ndbd-definition-maxnooflocalscans">MaxNoOfLocalScans</link></literal></entry> <entry>integer</entry> - <entry><literal>UNDEFINED</literal> (see <link linkend="mysql-cluster-param-ndbd-definition-maxnooflocalscans">description</link>)</entry> + <entry><literal>UNDEFINED</literal> (see + <link linkend="mysql-cluster-param-ndbd-definition-maxnooflocalscans">description</link>)</entry> <entry>32</entry> <entry>4294967039</entry> <entry>N</entry> @@ -12280,94 +12281,99 @@ </itemizedlist> </section> - + <section id="mysql-cluster-sql-statements"> + <title>Quick Reference: MySQL Cluster SQL Statements</title> - + <indexterm> <primary>MySQL Cluster</primary> <secondary>SQL statements for monitoring</secondary> </indexterm> - + <indexterm> <primary>SQL statements relating to MySQL Cluster</primary> </indexterm> - + <para> This section discusses several SQL statements that can prove useful in managing and monitoring a MySQL server that is connected to a MySQL Cluster, and in some cases provide - information about the cluster itself. + information about the cluster itself. </para> - + <itemizedlist> + <indexterm> <primary>SHOW ENGINE</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <indexterm> <primary>SHOW ENGINE NDB STATUS</primary> </indexterm> - + <indexterm> <primary>SHOW ENGINE NDBCLUSTER STATUS</primary> </indexterm> + <listitem> <para> <literal>SHOW ENGINE NDB STATUS</literal>, <literal>SHOW - ENGINE NDBCLUSTER STATUS</literal> + ENGINE NDBCLUSTER STATUS</literal> </para> - + <para> The output of this statement contains information about the server's connection to the cluster, creation and usage of MySQL Cluster objects, and binary logging for MySQL Cluster replication. </para> - + <para> See <xref linkend="show-engine"/>, for a usage example and more detailed information. </para> </listitem> - + <listitem> <indexterm> <primary>SHOW ENGINES</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> + <para> <literal>SHOW ENGINES [LIKE 'NDB%']</literal> </para> - + <para> This statement can be used to determine whether or not clustering support is enabled in the MySQL server, and if so, whether it is active. </para> - + <para> See <xref linkend="show-engines"/>, for more detailed information. </para> </listitem> - + <listitem> <indexterm> <primary>SHOW VARIABLES</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> + <para> <literal>SHOW VARIABLES LIKE 'NDB%'</literal> </para> - + <para> This statement provides a list of most server system variables relating to the <literal>NDB</literal> storage engine, and their values, as shown here: - - <programlisting> + +<programlisting> mysql> <userinput>SHOW VARIABLES LIKE 'NDB%';</userinput> +-------------------------------------+-------+ | Variable_name | Value | @@ -12387,22 +12393,23 @@ +-------------------------------------+-------+ </programlisting> </para> - + <para> See <xref linkend="server-system-variables"/>, for more information. </para> </listitem> - + <listitem> <indexterm> <primary>SHOW STATUS</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> + <para> <literal>SHOW STATUS LIKE 'NDB%'</literal> </para> - + <para> This statement shows at a glance whether or not the MySQL server is acting as a cluster SQL node, and if so, it @@ -12410,8 +12417,8 @@ and port for the cluster management server to which it is connected, and the number of data nodes in the cluster, as shown here: - - <programlisting> + +<programlisting> mysql> <userinput>SHOW STATUS LIKE 'NDB%';</userinput> +--------------------------+---------------+ | Variable_name | Value | @@ -12421,13 +12428,13 @@ | Ndb_config_from_port | 1186 | | Ndb_number_of_data_nodes | 4 | +--------------------------+---------------+ -</programlisting> - +</programlisting> + If the MySQL server was built with clustering support, but it is not connected to a cluster, all rows in the output of this statement contain a zero or an empty string: - - <programlisting> + +<programlisting> mysql> <userinput>SHOW STATUS LIKE 'NDB%';</userinput> +--------------------------+-------+ | Variable_name | Value | @@ -12437,15 +12444,16 @@ | Ndb_config_from_port | 0 | | Ndb_number_of_data_nodes | 0 | +--------------------------+-------+ -</programlisting> +</programlisting> </para> - + <para> See also <xref linkend="show-status"/>. </para> </listitem> + </itemizedlist> - + </section> </section> @@ -17104,21 +17112,20 @@ indexed. </para> </listitem> - + <listitem> <para> You cannot create indexes on <literal>NDB</literal> table columns that use any of the <literal>TEXT</literal> or - <literal>BLOB</literal> data types. + <literal>BLOB</literal> data types. </para> - + <para> - The <literal>NDB</literal> storage - engine also does not support <literal>FULLTEXT</literal> - indexes (these are supported by <literal>MyISAM</literal> - only). + The <literal>NDB</literal> storage engine also does not + support <literal>FULLTEXT</literal> indexes (these are + supported by <literal>MyISAM</literal> only). </para> - + <para> However, you can index <literal>VARCHAR</literal> columns of <literal>NDB</literal> tables. Modified: trunk/refman-5.0/mysql-cluster.xml =================================================================== --- trunk/refman-5.0/mysql-cluster.xml 2007-03-09 12:52:29 UTC (rev 5275) +++ trunk/refman-5.0/mysql-cluster.xml 2007-03-09 12:53:52 UTC (rev 5276) Changed blocks: 11, Lines Added: 63, Lines Deleted: 55; 10298 bytes @@ -870,7 +870,7 @@ <primary>MySQL Cluster</primary> <secondary>and DNS</secondary> </indexterm> - + <para> In the interest of simplicity (and reliability), this How-To uses only numeric IP addresses. However, if DNS resolution is @@ -880,11 +880,11 @@ operating system's equivalent for providing a means to do host lookup if such is available. </para> - + <remark role="NOTE"> [js] Candidate for Troubleshooting Guide? </remark> - + <note> <para> A common problem when trying to use hostnames for Cluster @@ -898,45 +898,45 @@ (including some derivatives such as CentOS and Fedora) places the following entries in these machines' <filename>/etc/hosts</filename> files: - + <programlisting> # ndb1 <filename>/etc/hosts</filename>: 127.0.0.1 ndb1.cluster ndb1 localhost.localdomain localhost </programlisting> - + <programlisting> # ndb2 <filename>/etc/hosts</filename>: 127.0.0.1 ndb2.cluster ndb2 localhost.localdomain localhost </programlisting> - - SuSE Linux (including OpenSuSE) places - these entries in the machines' - <filename>/etc/hosts</filename> files: - + + SuSE Linux (including OpenSuSE) places these entries in the + machines' <filename>/etc/hosts</filename> files: + <programlisting> # ndb1 <filename>/etc/hosts</filename>: 127.0.0.1 localhost 127.0.0.2 ndb1.cluster ndb1 </programlisting> - + <programlisting> # ndb2 <filename>/etc/hosts</filename>: 127.0.0.1 localhost 127.0.0.2 ndb2.cluster ndb2 </programlisting> - + In both instances, <literal>ndb1</literal> routes <literal>ndb1.cluster</literal> to a loopback IP address, but gets a public IP address from DNS for - <literal>ndb2.cluster</literal>, while <literal>ndb2</literal> - routes <literal>ndb2.cluster</literal> to a loopback address - and obtains a public address for + <literal>ndb2.cluster</literal>, while + <literal>ndb2</literal> routes + <literal>ndb2.cluster</literal> to a loopback address and + obtains a public address for <literal>ndb1.cluster</literal>. The result is that each data node connects to the management server, but cannot tell when any other data nodes have connected, and so the data nodes appear to hang while starting. </para> - + <para> You should also be aware that you cannot mix <literal>localhost</literal> and other hostnames or IP @@ -3214,7 +3214,7 @@ set it on the command line or in the <filename>my.cnf</filename> file for each executable. </para> - + <para> The maximum length of a connectstring is 1024 characters. </para> @@ -7517,7 +7517,8 @@ <row> <entry><literal><link linkend="mysql-cluster-param-ndbd-definition-maxnooflocalscans">MaxNoOfLocalScans</link></literal></entry> <entry>integer</entry> - <entry><literal>UNDEFINED</literal> (see <link linkend="mysql-cluster-param-ndbd-definition-maxnooflocalscans">description</link>)</entry> + <entry><literal>UNDEFINED</literal> (see + <link linkend="mysql-cluster-param-ndbd-definition-maxnooflocalscans">description</link>)</entry> <entry>32</entry> <entry>4294967039</entry> <entry>N</entry> @@ -12386,93 +12387,99 @@ </itemizedlist> </section> + <section id="mysql-cluster-sql-statements"> + <title>Quick Reference: MySQL Cluster SQL Statements</title> - + <indexterm> <primary>MySQL Cluster</primary> <secondary>SQL statements for monitoring</secondary> </indexterm> - + <indexterm> <primary>SQL statements relating to MySQL Cluster</primary> </indexterm> - + <para> This section discusses several SQL statements that can prove useful in managing and monitoring a MySQL server that is connected to a MySQL Cluster, and in some cases provide - information about the cluster itself. + information about the cluster itself. </para> - + <itemizedlist> + <indexterm> <primary>SHOW ENGINE</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <indexterm> <primary>SHOW ENGINE NDB STATUS</primary> </indexterm> - + <indexterm> <primary>SHOW ENGINE NDBCLUSTER STATUS</primary> </indexterm> + <listitem> <para> <literal>SHOW ENGINE NDB STATUS</literal>, <literal>SHOW - ENGINE NDBCLUSTER STATUS</literal> + ENGINE NDBCLUSTER STATUS</literal> </para> - + <para> The output of this statement contains information about the server's connection to the cluster, creation and usage of MySQL Cluster objects, and binary logging for MySQL Cluster replication. </para> - + <para> See <xref linkend="show-engine"/>, for a usage example and more detailed information. </para> </listitem> - + <listitem> <indexterm> <primary>SHOW ENGINES</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> + <para> <literal>SHOW ENGINES [LIKE 'NDB%']</literal> </para> - + <para> This statement can be used to determine whether or not clustering support is enabled in the MySQL server, and if so, whether it is active. </para> - + <para> See <xref linkend="show-engines"/>, for more detailed information. </para> </listitem> - + <listitem> <indexterm> <primary>SHOW VARIABLES</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> + <para> <literal>SHOW VARIABLES LIKE 'NDB%'</literal> </para> - + <para> This statement provides a list of most server system variables relating to the <literal>NDB</literal> storage engine, and their values, as shown here: - - <programlisting> + +<programlisting> mysql> <userinput>SHOW VARIABLES LIKE 'NDB%';</userinput> +-------------------------------------+-------+ | Variable_name | Value | @@ -12492,22 +12499,23 @@ +-------------------------------------+-------+ </programlisting> </para> - + <para> See <xref linkend="server-system-variables"/>, for more information. </para> </listitem> - + <listitem> <indexterm> <primary>SHOW STATUS</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> + <para> <literal>SHOW STATUS LIKE 'NDB%'</literal> </para> - + <para> This statement shows at a glance whether or not the MySQL server is acting as a cluster SQL node, and if so, it @@ -12515,8 +12523,8 @@ and port for the cluster management server to which it is connected, and the number of data nodes in the cluster, as shown here: - - <programlisting> + +<programlisting> mysql> <userinput>SHOW STATUS LIKE 'NDB%';</userinput> +--------------------------+---------------+ | Variable_name | Value | @@ -12526,13 +12534,13 @@ | Ndb_config_from_port | 1186 | | Ndb_number_of_data_nodes | 4 | +--------------------------+---------------+ -</programlisting> - +</programlisting> + If the MySQL server was built with clustering support, but it is not connected to a cluster, all rows in the output of this statement contain a zero or an empty string: - - <programlisting> + +<programlisting> mysql> <userinput>SHOW STATUS LIKE 'NDB%';</userinput> +--------------------------+-------+ | Variable_name | Value | @@ -12542,15 +12550,16 @@ | Ndb_config_from_port | 0 | | Ndb_number_of_data_nodes | 0 | +--------------------------+-------+ -</programlisting> +</programlisting> </para> - + <para> See also <xref linkend="show-status"/>. </para> </listitem> + </itemizedlist> - + </section> </section> @@ -17201,21 +17210,20 @@ Temporary tables are not supported. </para> </listitem> - + <listitem> <para> You cannot create indexes on <literal>NDB</literal> table columns that use any of the <literal>TEXT</literal> or - <literal>BLOB</literal> data types. + <literal>BLOB</literal> data types. </para> - + <para> - The <literal>NDB</literal> storage - engine also does not support <literal>FULLTEXT</literal> - indexes (these are supported by <literal>MyISAM</literal> - only). + The <literal>NDB</literal> storage engine also does not + support <literal>FULLTEXT</literal> indexes (these are + supported by <literal>MyISAM</literal> only). </para> - + <para> However, you can index <literal>VARCHAR</literal> columns of <literal>NDB</literal> tables. Modified: trunk/refman-5.1/mysql-cluster.xml =================================================================== --- trunk/refman-5.1/mysql-cluster.xml 2007-03-09 12:52:29 UTC (rev 5275) +++ trunk/refman-5.1/mysql-cluster.xml 2007-03-09 12:53:52 UTC (rev 5276) Changed blocks: 12, Lines Added: 66, Lines Deleted: 65; 10852 bytes @@ -3147,7 +3147,7 @@ set it on the command line or in the <filename>my.cnf</filename> file for each executable. </para> - + <para> The maximum length of a connectstring is 1024 characters. </para> @@ -12534,80 +12534,82 @@ </itemizedlist> </section> - + <section id="mysql-cluster-sql-statements"> + <title>Quick Reference: MySQL Cluster SQL Statements</title> - + <indexterm> <primary>MySQL Cluster</primary> <secondary>SQL statements for monitoring</secondary> </indexterm> - + <indexterm> <primary>SQL statements relating to MySQL Cluster</primary> </indexterm> - + <para> This section discusses several SQL statements that can prove useful in managing and monitoring a MySQL server that is connected to a MySQL Cluster, and in some cases provide - information about the cluster itself. + information about the cluster itself. </para> - + <itemizedlist> + <listitem> <indexterm> <primary>SHOW ENGINE</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <indexterm> <primary>SHOW ENGINE NDB STATUS</primary> </indexterm> - + <indexterm> <primary>SHOW ENGINE NDBCLUSTER STATUS</primary> </indexterm> - + <para> <literal>SHOW ENGINE NDB STATUS</literal>, <literal>SHOW ENGINE NDBCLUSTER STATUS</literal> </para> - + <para> The output of this statement contains information about the server's connection to the cluster, creation and usage of MySQL Cluster objects, and binary logging for MySQL Cluster replication. </para> - + <para> See <xref linkend="show-engine"/>, for a usage example and more detailed information. </para> </listitem> - + <listitem> <indexterm> <primary>SHOW ENGINES</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <para> <literal>SHOW ENGINES</literal> </para> - + <para> This statement can be used to determine whether or not clustering support is enabled in the MySQL server, and if so, whether it is active. </para> - + <para> See <xref linkend="show-engines"/>, for more detailed information. </para> - + <note> <para> In MySQL 5.1, this statement no longer supports a @@ -12618,18 +12620,18 @@ </para> </note> </listitem> - + <listitem> <indexterm> <primary>INFORMATION_SCHEMA.ENGINES table</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <para> <literal>SELECT * FROM INFORMATION_SCHEMA.ENGINES [WHERE - ENGINE LIKE 'NDB%']</literal> + ENGINE LIKE 'NDB%']</literal> </para> - + <para> This is the equivalent of <literal>SHOW ENGINES</literal>, but uses the <literal>ENGINES</literal> table of the @@ -12642,7 +12644,7 @@ shows whether the server was built with <literal>NDB</literal> support and, if so, whether it is enabled: - + <programlisting> mysql> <userinput>SELECT SUPPORT FROM INFORMATION_SCHEMA.ENGINES</userinput> -> <userinput>WHERE ENGINE LIKE 'NDB%';</userinput> @@ -12651,29 +12653,29 @@ +---------+ | ENABLED | +---------+ -</programlisting> +</programlisting> </para> - + <para> See <xref linkend="engines-table"/>, for more information. </para> </listitem> - + <listitem> <indexterm> <primary>SHOW VARIABLES</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <para> <literal>SHOW VARIABLES LIKE 'NDB%'</literal> </para> - + <para> This statement provides a list of most server system variables relating to the <literal>NDB</literal> storage engine, and their values, as shown here: - + <programlisting> mysql> <userinput>SHOW VARIABLES LIKE 'NDB%';</userinput> +-------------------------------------+-------+ @@ -12694,29 +12696,29 @@ +-------------------------------------+-------+ </programlisting> </para> - + <para> See <xref linkend="server-system-variables"/>, for more information. </para> </listitem> - + <listitem> <indexterm> <primary>INFORMATION_SCHEMA.GLOBAL_VARIABLES table</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <para> <literal>SELECT * FROM INFORMATION_SCHEMA.GLOBAL_VARIABLES - WHERE VARIABLE_NAME LIKE 'NDB%';</literal> + WHERE VARIABLE_NAME LIKE 'NDB%';</literal> </para> - + <para> This statement is the equivalent of the <literal>SHOW</literal> described in the previous item, and provides almost identical output, as shown here: - + <programlisting> mysql> <userinput>SELECT * FROM INFORMATION_SCHEMA.GLOBAL_VARIABLES</userinput> -> <userinput>WHERE VARIABLE_NAME LIKE 'NDB%';</userinput> @@ -12737,10 +12739,10 @@ | NDB_USE_TRANSACTIONS | ON | +-------------------------------------+----------------+ </programlisting> - + Unlike the case with the <literal>SHOW</literal> statement, it is possible to select individual columns. For example: - + <programlisting> mysql> <userinput>SELECT VARIABLE_VALUE </userinput> -> <userinput>FROM INFORMATION_SCHEMA.GLOBAL_VARIABLES</userinput> @@ -12750,26 +12752,26 @@ +----------------+ | ON | +----------------+ -</programlisting> +</programlisting> </para> - + <para> - See <xref linkend="variables-table"/>, and + See <xref linkend="variables-table"/>, and <xref linkend="server-system-variables"/>, for more information. </para> </listitem> - + <listitem> <indexterm> <primary>SHOW STATUS</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <para> <literal>SHOW STATUS LIKE 'NDB%'</literal> </para> - + <para> This statement shows at a glance whether or not the MySQL server is acting as a cluster SQL node, and if so, it @@ -12777,7 +12779,7 @@ and port for the cluster management server to which it is connected, and the number of data nodes in the cluster, as shown here: - + <programlisting> mysql> <userinput>SHOW STATUS LIKE 'NDB%';</userinput> +--------------------------+---------------+ @@ -12788,12 +12790,12 @@ | Ndb_config_from_port | 1186 | | Ndb_number_of_data_nodes | 4 | +--------------------------+---------------+ -</programlisting> - +</programlisting> + If the MySQL server was built with clustering support, but it is not connected to a cluster, all rows in the output of this statement contain a zero or an empty string: - + <programlisting> mysql> <userinput>SHOW STATUS LIKE 'NDB%';</userinput> +--------------------------+-------+ @@ -12804,43 +12806,43 @@ | Ndb_config_from_port | 0 | | Ndb_number_of_data_nodes | 0 | +--------------------------+-------+ -</programlisting> +</programlisting> </para> - + <para> See also <xref linkend="show-status"/>. </para> </listitem> - + <listitem> <indexterm> <primary>INFORMATION_SCHEMA.GLOBAL_STATUS table</primary> <secondary>used with MySQL Cluster</secondary> </indexterm> - + <para> <literal>SELECT * FROM INFORMATION_SCHEMA.GLOBAL_STATUS - WHERE VARIABLE_NAME LIKE 'NDB%';</literal> + WHERE VARIABLE_NAME LIKE 'NDB%';</literal> </para> - + <para> Beginning with MySQL 5.1.12, this statement provides similar output to the <literal>SHOW</literal> statement discussed in the previous item. However, unlike the case with <literal>SHOW STATUS</literal>, it is possible using the <literal>SELECT</literal> to extract values in SQL for use - in scripts for monitoring and automation purposes. + in scripts for monitoring and automation purposes. </para> - + <para> See <xref linkend="status-table"/>, for more information. </para> </listitem> + </itemizedlist> - + </section> - - + </section> <section id="mysql-cluster-backup"> @@ -19784,21 +19786,20 @@ Temporary tables are not supported. </para> </listitem> - + <listitem> <para> You cannot create indexes on <literal>NDB</literal> table columns that use any of the <literal>TEXT</literal> or - <literal>BLOB</literal> data types. + <literal>BLOB</literal> data types. </para> - + <para> - The <literal>NDB</literal> storage - engine also does not support <literal>FULLTEXT</literal> - indexes (these are supported by <literal>MyISAM</literal> - only). + The <literal>NDB</literal> storage engine also does not + support <literal>FULLTEXT</literal> indexes (these are + supported by <literal>MyISAM</literal> only). </para> - + <para> However, you can index <literal>VARCHAR</literal> columns of <literal>NDB</literal> tables.
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r5276 - branches/telcos/refman-5.1 trunk/refman-4.1 trunk/refman-5.0 trunk/refman-5.1 | jon | 9 Mar |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.919 sec. using MySQL 5.1.14-beta-log