| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | September 5 2007 7:38am |
| Subject: | svn commit - mysqldoc@docsrva: r7669 - trunk/refman-5.2 | ||
| View as plain text | |||
Author: jstephens Date: 2007-09-05 07:37:59 +0200 (Wed, 05 Sep 2007) New Revision: 7669 Log: Commented out &mccge-* entities in 5.2 Manual, for now. (Thanks, Paul!) Modified: trunk/refman-5.2/mysql-cluster.xml Modified: trunk/refman-5.2/mysql-cluster.xml =================================================================== --- trunk/refman-5.2/mysql-cluster.xml 2007-09-05 01:12:06 UTC (rev 7668) +++ trunk/refman-5.2/mysql-cluster.xml 2007-09-05 05:37:59 UTC (rev 7669) Changed blocks: 56, Lines Added: 81, Lines Deleted: 82; 20440 bytes @@ -42,13 +42,13 @@ in MySQL ¤t-series; binary releases and in RPMs compatible with most modern Linux distributions. </para> - +<!-- <note> <para> Binary releases and RPMs are not available for &mccge-series;, which must be built from source. </para> - </note> + </note>--> <indexterm> <primary>MySQL Cluster</primary> @@ -1904,7 +1904,7 @@ <xref linkend="installing-source-tree"/>.) </para> - &mccge-warning-unsupported-begin; + <!--&mccge-warning-unsupported-begin;--> <para> RPMs are also available for both 32-bit and 64-bit Linux @@ -1985,7 +1985,7 @@ <xref linkend="mysql-cluster-multi-config"/>. </para> - &mccge-warning-end-cluster; + <!--&mccge-warning-end-cluster;--> <note> <para> @@ -2121,7 +2121,7 @@ on each machine where a data node or SQL node is to reside. </para> - &mccge-warning-unsupported-begin; + <!--&mccge-warning-unsupported-begin;--> <formalpara> @@ -2155,7 +2155,7 @@ automatically. </para> - &mccge-warning-unsupported-begin; + <!--&mccge-warning-unsupported-begin;--> <para> <emphasis role="bold">Data Node Installation — RPM @@ -2181,7 +2181,7 @@ directory. </para> - &mccge-warning-end-cluster; + <!--&mccge-warning-end-cluster;--> <para> <emphasis role="bold">Management Node Installation — @@ -2245,7 +2245,7 @@ </orderedlist> - &mccge-warning-unsupported-begin; + <!--&mccge-warning-unsupported-begin;--> <para> <emphasis role="bold">Management Node Installation — RPM @@ -2570,7 +2570,7 @@ </listitem> <listitem> - &mccge-warning-unsupported-begin; + <!--&mccge-warning-unsupported-begin;--> <para> If you used RPM files to install MySQL on the cluster host @@ -2582,7 +2582,7 @@ </orderedlist> - &mccge-warning-end-cluster; + <!--&mccge-warning-end-cluster;--> <indexterm> <primary>MySQL Cluster</primary> @@ -3176,7 +3176,7 @@ <xref linkend="installing-source-tree"/>. </para> - &mccge-warning-begin; + <!--&mccge-warning-begin; <warning> <para> @@ -3198,7 +3198,7 @@ </para> </warning> - &mccge-warning-end-cluster; + &mccge-warning-end-cluster;--> <para> <command>BUILD/compile-pentium-max</command> also includes @@ -4317,9 +4317,9 @@ </para> <para> - Beginning with MySQL 5.1.16 + Beginning with MySQL 5.1.16<!-- (<emphasis>&mccge-series;</emphasis>: MySQL - 5.1.15-ndb-6.1.3), it is possible to disable arbitration + 5.1.15-ndb-6.1.3)-->, it is possible to disable arbitration completely by setting <literal>ArbitrationRank</literal> to 0 on all management and SQL nodes. </para> @@ -4524,7 +4524,7 @@ <listitem> - &mccge-warning-begin; + <!--&mccge-warning-begin;--> <para id="mysql-cluster-param-ndbd-definition-tcpbind-inaddr-any"> <literal>TcpBind_INADDR_ANY</literal> @@ -4537,12 +4537,12 @@ autogenerated connections). The default is <literal>FALSE</literal> (<literal>0</literal>). </para> - +<!-- <para> This parameter was added in MySQL 5.1.16-ndb-6.2.0. </para> - &mccge-warning-end-cluster; + &mccge-warning-end-cluster;--> </listitem> @@ -5563,7 +5563,7 @@ <primary><literal>FragmentLogFileSize</literal></primary> </indexterm> - &mccge-warning-begin; + <!--&mccge-warning-begin;--> <para id="mysql-cluster-param-ndbd-definition-fragmentlogfilesize"> <literal>FragmentLogFileSize</literal> @@ -5575,7 +5575,7 @@ <literal>16M</literal>. </para> - &mccge-warning-end-cluster; + <!--&mccge-warning-end-cluster;--> </listitem> @@ -5881,8 +5881,8 @@ </para> <para> - Beginning with MySQL 5.1.15 (&mccge-series;: MySQL - 5.1.15-ndb-6.1.1), this parameter takes one of the integer + Beginning with MySQL 5.1.15<!-- (&mccge-series;: MySQL + 5.1.15-ndb-6.1.1)-->, this parameter takes one of the integer values <literal>0</literal>, <literal>1</literal>, or <literal>2</literal>, which act as follows: </para> @@ -6008,7 +6008,7 @@ <warning> <para> - When using MySQL Cluster or &mccge-series; on Linux, + When using MySQL Cluster<!-- or &mccge-series;--> on Linux, <literal>ODirect</literal> should be enabled for 2.6 or newer kernels. </para> @@ -7167,8 +7167,8 @@ </para> <para> - This parameter was added in MySQL Cluster 5.1.16. - (&mccge-series;: MySQL Cluster 5.1.14-ndb-6.1.0). + This parameter was added in MySQL Cluster 5.1.16<!--. + (&mccge-series;: MySQL Cluster 5.1.14-ndb-6.1.0)-->. </para> </listitem> @@ -7294,7 +7294,7 @@ <primary>BackupReportFrequency</primary> </indexterm> - &mccge-warning-begin; + <!--&mccge-warning-begin;--> <para id="mysql-cluster-param-ndbd-definition-backupreportfrequency"> This parameter controls how often backup status reports @@ -7310,12 +7310,12 @@ <para> The default value is 0. </para> - +<!-- <para> This parameter was added in MySQL 5.1.19-ndb-6.2.3. </para> - &mccge-warning-end-cluster; + &mccge-warning-end-cluster;--> </listitem> @@ -7508,9 +7508,9 @@ </para> <para> - Beginning with MySQL 5.1.16 + Beginning with MySQL 5.1.16<!-- (<emphasis>&mccge-series;</emphasis>: MySQL - 5.1.15-ndb-6.1.3), it is possible to disable arbitration + 5.1.15-ndb-6.1.3)-->, it is possible to disable arbitration completely by setting <literal>ArbitrationRank</literal> to 0 on all management and SQL nodes. </para> @@ -8671,8 +8671,8 @@ </row> <row> <entry><literal><link linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory">LockPagesInMainMemory</link></literal></entry> - <entry><emphasis>As of MySQL 5.1.15 (&mccge-series;: MySQL - 5.1.15-ndb-6.1.1)</emphasis>: integer; + <entry><emphasis>As of MySQL 5.1.15<!-- (&mccge-series;: MySQL + 5.1.15-ndb-6.1.1)--></emphasis>: integer; <emphasis>previously</emphasis>: true|false (<literal>1</literal>|<literal>0</literal>)</entry> <entry>0</entry> @@ -8896,8 +8896,8 @@ </row> <row> <entry><literal><link linkend="mysql-cluster-param-ndbd-definition-memreportfrequency">MemReportFrequency</link></literal> - (added in MySQL 5.1.16; &mccge-series;: added in MySQL - 5.1.14-ndb-6.1.0)</entry> + (added in MySQL 5.1.16<!--; &mccge-series;: added in MySQL + 5.1.14-ndb-6.1.0-->)</entry> <entry>integer</entry> <entry>0</entry> <entry>0</entry> @@ -9042,8 +9042,8 @@ </row> <row> <entry><literal><link linkend="mysql-cluster-param-ndbd-definition-tcpbind-inaddr-any">TcpBind_INADDR_ANY</link></literal> - (<emphasis>&mccge-series; only</emphasis>: added in - MySQL 5.1.16-ndb-6.2.0)</entry> + <!--(<emphasis>&mccge-series; only</emphasis>: added in + MySQL 5.1.16-ndb-6.2.0)--></entry> <entry>true|false (<literal>1</literal>|<literal>0</literal>)</entry> <entry>1</entry> <entry>0</entry> @@ -9742,12 +9742,12 @@ downgrade. See <xref linkend="mysql-cluster-configuration"/>. </para> - <para> + <!--<para> For information about upgrading or downgrading between &mccge-series; releases, or between &mccge-series; releases and mainline MySQL releases, see the changelogs relating to &mccge-series;. - </para> + </para>--> <para> This section remains in development, and continues to be updated @@ -10273,7 +10273,7 @@ 5.1.17 or earlier to MySQL 5.1.18 or later. </para> - <para> + <!--<para> For users of &mccge-series; the relevant versions are as follows: @@ -10306,7 +10306,7 @@ </listitem> </itemizedlist> - </para> + </para>--> </listitem> </itemizedlist> @@ -12577,7 +12577,7 @@ <primary><literal>REPORT</literal> command (MySQL Cluster)</primary> </indexterm> - &mccge-warning-begin; + <!--&mccge-warning-begin;--> <para> <literal><replaceable>node_id</replaceable> REPORT @@ -12602,7 +12602,7 @@ The REPORT command was introduced in MySQL 5.1.8-ndb-6.2.3. </para> - &mccge-warning-end-cluster; + <!--&mccge-warning-end-cluster;--> </listitem> @@ -15108,7 +15108,7 @@ present in the data node's <literal>DataDir</literal>.) </para> - &mccge-warning-unsupported-begin; + <!--&mccge-warning-unsupported-begin;--> <para> It is possible to restore data without restoring table @@ -15133,7 +15133,7 @@ notice</emphasis>. (Bug #24363) </para> - &mccge-warning-end-cluster; + <!--&mccge-warning-end-cluster;--> <para> The <option>-b</option> option is used to specify the ID or @@ -15392,8 +15392,8 @@ <row> <entry><option>--skip-table-check</option></entry> <entry><option>-s</option></entry> - <entry>Do not check table schemas (Added in MySQL 5.1.17; <emphasis>not - supported in &mccge-series;</emphasis>)</entry> + <entry>Do not check table schemas (Added in MySQL 5.1.17<!--; <emphasis>not + supported in &mccge-series;</emphasis>)--></entry> <entry><literal>FALSE</literal></entry> </row> <row> @@ -15406,7 +15406,7 @@ </tgroup> </informaltable> - &mccge-warning-unsupported-begin; + <!--&mccge-warning-unsupported-begin;--> <para> Beginning with MySQL 5.1.18, several additional options are @@ -15524,7 +15524,7 @@ </itemizedlist> </para> - &mccge-warning-end-cluster; + <!--&mccge-warning-end-cluster;--> <indexterm> <primary><command>ndb_restore</command></primary> @@ -15963,7 +15963,7 @@ management client command <literal>ALL STATUS</literal>. </para> </listitem> - +<!-- <listitem> &mccge-warning-begin; @@ -15983,7 +15983,7 @@ &mccge-warning-end-cluster; - </listitem> + </listitem>--> </itemizedlist> @@ -16018,7 +16018,7 @@ <listitem> <para> <command>ndbd_redo_log_reader</command> - (<emphasis>&mccge-series; only</emphasis>) + <!--(<emphasis>&mccge-series; only</emphasis>)--> </para> </listitem> @@ -17471,7 +17471,7 @@ <manvolnum>1</manvolnum> <refmiscinfo class="manual">MySQL Database System</refmiscinfo> <refmiscinfo class="source">MySQL</refmiscinfo> - <refmiscinfo class="version">&mccge-series;</refmiscinfo> + <!--<refmiscinfo class="version">&mccge-series;</refmiscinfo>--> <refmiscinfo class="refman">Check and Print Content of Cluster Redo Log</refmiscinfo> </refmeta> @@ -17490,9 +17490,9 @@ <refsection id="ndb-redo-log-reader"> <title>Description</title> - +<!-- &mccge-warning-section; - +--> <para> Reads a redo log file, checking it for errors, printing its contents in a human-readable format, or both. @@ -17502,9 +17502,9 @@ </para> <para> - This utility was made available as part of the default + This utility<!-- was made available as part of the default builds of &mccge-series; beginning with MySQL - 5.1.15-ndb-6.1.3. It remains under development, and its + 5.1.15-ndb-6.1.3. It--> remains under development, and its syntax and behavior are subject to change in future releases. For this reason, it should be considered experimental at this time. @@ -19262,9 +19262,8 @@ </para> </formalpara> - +<!-- &mccge-warning-unsupported-begin; - <para> Beginning with MySQL 5.1.18, this limitation is lifted, as discussed in the next few paragraphs, in which we consider @@ -19293,7 +19292,7 @@ <para> All SQL nodes acting as replication masters and slaves are started using the - <option>--log-slave-updates</option> option + <option>&ddash;log-slave-updates</option> option </para> </listitem> @@ -19339,7 +19338,7 @@ In this case, different SQL nodes in each cluster are used as replication masters and slaves. However, you must <emphasis>not</emphasis> start any of the SQL nodes using - <option>--log-slave-updates</option> (see the + <option>&ddash;log-slave-updates</option> (see the <link linkend="option_mysqld_log-slave-updates">description of this option</link> for more information). This type of circular replication scheme for MySQL Cluster, in which the @@ -19348,9 +19347,9 @@ should be noted that it has not yet been thoroughly tested and must therefore still be considered experimental. </para> - + &mccge-warning-end-cluster; - +--> </listitem> <listitem> @@ -20095,9 +20094,9 @@ are covered in <xref linkend="mysql-cluster-replication-two-channels"/>. </para> - +<!-- &mccge-warning-begin; - + --> <indexterm> <primary>batched updates (MySQL Cluster Replication)</primary> </indexterm> @@ -20169,11 +20168,11 @@ 6 rows in set (0.00 sec) </programlisting> </para> - +<!-- &mccge-warning-end-cluster; +--> - </section> <section id="mysql-cluster-replication-two-channels"> @@ -21016,9 +21015,9 @@ <primary>conflict resolution</primary> <secondary>in MySQL Cluster Replication</secondary> </indexterm> - +<!-- &mccge-warning-section; - +--> <para> When using a replication setup involving multiple masters, it is possible that different masters may try to update the same row @@ -23096,19 +23095,19 @@ <para> In the sections that follow, we discuss known limitations in MySQL - ¤t-series; Cluster and &mccge-series; releases as compared + ¤t-series; Cluster<!-- and &mccge-series;--> releases as compared with the features available when using the <literal>MyISAM</literal> and <literal>InnoDB</literal> storage engines. Currently, there are no plans to address these in coming - releases of MySQL ¤t-series; or &mccge-series;; however, we + releases of MySQL ¤t-series;<!-- or &mccge-series;-->; however, we will attempt to supply fixes for these issues in subsequent release series. If you check the <quote>Cluster</quote> category in the MySQL bugs database at <ulink url="http://bugs.mysql.com"/>, you can find known bugs which (if marked <quote>¤t-series;</quote>) we intend to - correct in upcoming releases of MySQL ¤t-series;. Some of + correct in upcoming releases of MySQL ¤t-series;.<!-- Some of these issues may be addressed in &mccge-series; and the fixes - included in a future mainline MySQL Cluster version. + included in a future mainline MySQL Cluster version.--> </para> <para> @@ -23592,21 +23591,21 @@ <listitem> <para> The maximum number of metadata objects in - MySQL ¤t-series; Cluster and - &mccge-series; is 20320. This limit is + MySQL ¤t-series; Cluster<!-- and + &mccge-series;--> is 20320. This limit is hard-coded. </para> </listitem> </itemizedlist> - <note> + <!--<note> <para role="mccge-warning"> &mccge-series; users should see <xref linkend="mysql-cluster-limitations-resolved"/>, for more information. </para> - </note> + </note>--> </para> </formalpara> @@ -24485,7 +24484,7 @@ concurrently on a single host, it is not always advisable to do so for reasons of performance and high availability, as well as other considerations. In particular, in MySQL - ¤t-series; or &mccge-series;, we do not support for + ¤t-series;<!-- or &mccge-series;-->, we do not support for production use any MySQL Cluster deployment in which more than one <command>ndbd</command> process is run on a single physical machine. @@ -24494,7 +24493,7 @@ <para> We may support multiple data nodes per host in a future MySQL release, following additional testing. However, in - MySQL ¤t-series; and &mccge-series;, such + MySQL ¤t-series;<!-- and &mccge-series;-->, such configurations can be considered experimental only. </para> </note> @@ -24544,7 +24543,7 @@ <para> A number of limitations and related issues existing in earlier versions of MySQL Cluster have been resolved over the course of - development of MySQL ¤t-series; or &mccge-series;: + development of MySQL ¤t-series;<!-- or &mccge-series;-->: <itemizedlist> @@ -24802,7 +24801,7 @@ <listitem> - &mccge-warning-begin; + <!--&mccge-warning-begin;--> <formalpara> <title>Maximum number of cluster nodes</title> @@ -24824,13 +24823,13 @@ nodes and management nodes beginning with this version is 63, of which up to 48 can be data nodes. </para> - +<!-- <para> The limitation that a data node cannot have a node ID greater than 49 continues to apply in &mccge-series;. </para> - &mccge-warning-end-cluster; + &mccge-warning-end-cluster;--> </listitem> </itemizedlist> @@ -24879,7 +24878,7 @@ <para> In this section, we discuss changes in the implementation of MySQL - Cluster in MySQL ¤t-series; and &mccge-series; as compared + Cluster in MySQL ¤t-series; <!--and &mccge-series;--> as compared to MySQL &previous-series;. <!--
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r7669 - trunk/refman-5.2 | jon | 5 Sep |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.670 sec. using MySQL 5.1.14-beta-log