| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | March 23 2007 12:51pm |
| Subject: | svn commit - mysqldoc@docsrva: r5522 - in trunk: refman-4.1 refman-5.0 refman-5.1 | ||
| View as plain text | |||
Author: jstephens Date: 2007-03-23 12:51:25 +0100 (Fri, 23 Mar 2007) New Revision: 5522 Log: Reformat. Modified: trunk/refman-4.1/mysql-cluster.xml trunk/refman-5.0/mysql-cluster.xml trunk/refman-5.0/releasenotes-es-5.0.xml trunk/refman-5.1/mysql-cluster.xml trunk/refman-5.1/news-5.1.xml Modified: trunk/refman-4.1/mysql-cluster.xml =================================================================== --- trunk/refman-4.1/mysql-cluster.xml 2007-03-23 11:50:30 UTC (rev 5521) +++ trunk/refman-4.1/mysql-cluster.xml 2007-03-23 11:51:25 UTC (rev 5522) Changed blocks: 2, Lines Added: 8, Lines Deleted: 8; 1838 bytes @@ -8304,10 +8304,10 @@ downgrading a MySQL Cluster from one MySQL release to another. It discusses different types of Cluster upgrades and downgrades, and provides a Cluster upgrade/downgrade compatibility matrix (see - <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>). You are expected - already to be familiar with installing and configuring a MySQL - Cluster prior to attempting an upgrade or downgrade. See - <xref linkend="mysql-cluster-configuration"/>. + <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>). + You are expected already to be familiar with installing and + configuring a MySQL Cluster prior to attempting an upgrade or + downgrade. See <xref linkend="mysql-cluster-configuration"/>. </para> <para> @@ -8492,14 +8492,14 @@ may be restarted using the <command>ndb_mgm</command> management client <literal>RESTART</literal> command. </para> - + <important> <para> When performing an upgrade or downgrade of the cluster software, you <emphasis>must</emphasis> upgrade or downgrade - the management nodes <emphasis>first</emphasis>, then the data nodes, and finally - the SQL nodes. Doing so in any other order may leave the - cluster in an unusable state. + the management nodes <emphasis>first</emphasis>, then the data + nodes, and finally the SQL nodes. Doing so in any other order + may leave the cluster in an unusable state. </para> </important> Modified: trunk/refman-5.0/mysql-cluster.xml =================================================================== --- trunk/refman-5.0/mysql-cluster.xml 2007-03-23 11:50:30 UTC (rev 5521) +++ trunk/refman-5.0/mysql-cluster.xml 2007-03-23 11:51:25 UTC (rev 5522) Changed blocks: 3, Lines Added: 10, Lines Deleted: 10; 2443 bytes @@ -8330,16 +8330,16 @@ <primary>downgrades</primary> <secondary>MySQL Cluster</secondary> </indexterm> - + <para> This portion of the MySQL Cluster chapter covers upgrading and downgrading a MySQL Cluster from one MySQL release to another. It discusses different types of Cluster upgrades and downgrades, and provides a Cluster upgrade/downgrade compatibility matrix (see - <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>). You are expected - already to be familiar with installing and configuring a MySQL - Cluster prior to attempting an upgrade or downgrade. See - <xref linkend="mysql-cluster-configuration"/>. + <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>). + You are expected already to be familiar with installing and + configuring a MySQL Cluster prior to attempting an upgrade or + downgrade. See <xref linkend="mysql-cluster-configuration"/>. </para> <para> @@ -8524,14 +8524,14 @@ may be restarted using the <command>ndb_mgm</command> management client <literal>RESTART</literal> command. </para> - + <important> <para> When performing an upgrade or downgrade of the cluster software, you <emphasis>must</emphasis> upgrade or downgrade - the management nodes <emphasis>first</emphasis>, then the data nodes, and finally - the SQL nodes. Doing so in any other order may leave the - cluster in an unusable state. + the management nodes <emphasis>first</emphasis>, then the data + nodes, and finally the SQL nodes. Doing so in any other order + may leave the cluster in an unusable state. </para> </important> @@ -13910,7 +13910,7 @@ <para> Specifies the connectstring to use in connecting to the management server. The format for the connectstring is - the same as described in + the same as described in <xref linkend="mysql-cluster-connectstring"/>, and defaults to <literal>localhost:1186</literal>. </para> Modified: trunk/refman-5.0/releasenotes-es-5.0.xml =================================================================== --- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-23 11:50:30 UTC (rev 5521) +++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-03-23 11:51:25 UTC (rev 5522) Changed blocks: 3, Lines Added: 18, Lines Deleted: 15; 2618 bytes @@ -76,21 +76,23 @@ </para> <itemizedlist> + <listitem> <para> <literal>NDB Cluster</literal>: It was not possible to set <literal>LockPagesInMainMemory</literal> equal to - <literal>0</literal>. (Bug #27291) + <literal>0</literal>. (Bug #27291) </para> </listitem> - + <listitem> <para> - <literal>NDB Cluster</literal>: A race condition could sometimes occur if the node - acting as master failed while node IDs were still being - allocated during startup. (Bug #27286) + <literal>NDB Cluster</literal>: A race condition could + sometimes occur if the node acting as master failed while node + IDs were still being allocated during startup. (Bug #27286) </para> </listitem> + <listitem> <para> <literal>NDB Cluster</literal>: When a data node was taking @@ -99,19 +101,20 @@ global checkpoints. (Bug #27283) </para> </listitem> - + <listitem> <para> - <literal>NDB Cluster</literal>: <command>mysqld</command> processes would sometimes crash - under high load. (Bug #26825) + <literal>NDB Cluster</literal>: <command>mysqld</command> + processes would sometimes crash under high load. (Bug #26825) </para> </listitem> - + <listitem> <para> - <literal>NDB Cluster</literal>: Some values of <literal>MaxNoOfTables</literal> - caused the error <errortext>Job buffer congestion</errortext> - to occur. (Bug #19378) + <literal>NDB Cluster</literal>: Some values of + <literal>MaxNoOfTables</literal> caused the error + <errortext>Job buffer congestion</errortext> to occur. (Bug + #19378) </para> </listitem> @@ -377,9 +380,9 @@ <listitem> <para> If a thread previously serviced a connection that was killed, - excessive memory and CPU use by the thread occurred if it later - serviced a connection that had to wait for a table lock. (Bug - #25966) + excessive memory and CPU use by the thread occurred if it + later serviced a connection that had to wait for a table lock. + (Bug #25966) </para> </listitem> Modified: trunk/refman-5.1/mysql-cluster.xml =================================================================== --- trunk/refman-5.1/mysql-cluster.xml 2007-03-23 11:50:30 UTC (rev 5521) +++ trunk/refman-5.1/mysql-cluster.xml 2007-03-23 11:51:25 UTC (rev 5522) Changed blocks: 11, Lines Added: 27, Lines Deleted: 20; 5180 bytes @@ -8359,7 +8359,7 @@ <literal>NoOfDiskPagesToDiskAfterRestartACC</literal> and <literal>NoOfDiskPagesToDiskAfterRestartTUP</literal> is approaching the amount of disk bandwidth available, you may wish - to increase the time between local checkpoints. + to increase the time between local checkpoints. </para> <para> @@ -8453,16 +8453,16 @@ <primary>downgrades</primary> <secondary>MySQL Cluster</secondary> </indexterm> - + <para> This portion of the MySQL Cluster chapter covers upgrading and downgrading a MySQL Cluster from one MySQL release to another. It discusses different types of Cluster upgrades and downgrades, and provides a Cluster upgrade/downgrade compatibility matrix (see - <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>). You are expected - already to be familiar with installing and configuring a MySQL - Cluster prior to attempting an upgrade or downgrade. See - <xref linkend="mysql-cluster-configuration"/>. + <xref linkend="mysql-cluster-upgrade-downgrade-compatibility"/>). + You are expected already to be familiar with installing and + configuring a MySQL Cluster prior to attempting an upgrade or + downgrade. See <xref linkend="mysql-cluster-configuration"/>. </para> <para> @@ -8647,14 +8647,14 @@ may be restarted using the <command>ndb_mgm</command> management client <literal>RESTART</literal> command. </para> - + <important> <para> When performing an upgrade or downgrade of the cluster software, you <emphasis>must</emphasis> upgrade or downgrade - the management nodes <emphasis>first</emphasis>, then the data nodes, and finally - the SQL nodes. Doing so in any other order may leave the - cluster in an unusable state. + the management nodes <emphasis>first</emphasis>, then the data + nodes, and finally the SQL nodes. Doing so in any other order + may leave the cluster in an unusable state. </para> </important> @@ -11740,9 +11740,8 @@ <entry>Node has been refused for inclusion in the cluster</entry> <entry>8</entry> <entry><literal>INFO</literal></entry> - <entry>Node cannot be included in cluster due to - misconfiguration, inability to establish - communication, or some other problem</entry> + <entry>Node cannot be included in cluster due to misconfiguration, inability to + establish communication, or some other problem</entry> </row> <row> <entry>data node neighbors</entry> @@ -17220,10 +17219,11 @@ exist on the slave, it is created by <command>ndb_restore</command>. (Bug #14612) </para> - + <remark> [js] Commenting out until I get answers to some questions... </remark> + <!-- <para> The <literal>ndb_schema</literal> table is defined as shown @@ -17244,6 +17244,7 @@ </programlisting> </para> --> + </section> <section id="mysql-cluster-replication-preparation"> @@ -18470,7 +18471,7 @@ one or more undo log files to it (an undo log file is also referred as an <firstterm>undofile</firstterm>). </para> - + <note> <para> In MySQL 5.1, undo log files are necessary only for Disk @@ -18780,11 +18781,13 @@ You may use absolute and relative filesystem paths with <literal>ADD UNDOFILE</literal> and <literal>ADD DATAFILE</literal>. Relative paths are calculated relative to - the data node's data directory. + the data node's data directory. + <remark role="note"> [js] Or maybe not... Have asked Jeb to resolve this issue. </remark> - <!--You may also use symbolic links.--> + +<!--You may also use symbolic links.--> </para> <para> @@ -18873,7 +18876,7 @@ </section> - <!--<section id="mysql-cluster-disk-data-symlinks"> +<!--<section id="mysql-cluster-disk-data-symlinks"> <title>Using Symbolic Links with Disk Data Objects</title> @@ -18978,7 +18981,9 @@ support more than one data node per host. </remark> - --><!-- + --> + +<!-- 4) Doing the same for multi data nodes running on one host. Give each data node its own path @@ -18997,7 +19002,9 @@ we then repeat the steps in step 2 placing the files in the desired location using symbolic links, and the step 3 for the actual create. - --><!-- + --> + +<!-- </para> </listitem> Modified: trunk/refman-5.1/news-5.1.xml =================================================================== --- trunk/refman-5.1/news-5.1.xml 2007-03-23 11:50:30 UTC (rev 5521) +++ trunk/refman-5.1/news-5.1.xml 2007-03-23 11:51:25 UTC (rev 5522) Changed blocks: 9, Lines Added: 41, Lines Deleted: 40; 6120 bytes @@ -231,16 +231,16 @@ </para> <itemizedlist> - + <listitem> <para> <literal>NDB Cluster</literal> (Cluster APIs): <literal>NAND</literal> and <literal>NOR</literal> operations with <literal>NdbScanFilter</literal> did not perform - correctly. (Bug #24568) + correctly. (Bug #24568) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal> (Cluster Replication): The @@ -248,7 +248,7 @@ cause replication to fail. (Bug #27005) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal> (Disk Data): Under some @@ -256,7 +256,7 @@ flushing Disk Data UNDO logs. (Bug #27102) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal> (Disk Data): Creating multiple @@ -264,24 +264,24 @@ cause the cluster to fail. (Bug #25992) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal> (Disk Data): <literal>ALTER - TABLE ... ADD COLUMN ...</literal> on a Disk Data table - moved data for existing non-indexed columns from the - tablespace into memory. (Bug #25880) + TABLE ... ADD COLUMN ...</literal> on a Disk Data table moved + data for existing non-indexed columns from the tablespace into + memory. (Bug #25880) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal> (Disk Data): <literal>DROP - INDEX</literal> on a Disk Data table did not always move data - from memory into the tablespace. (Bug #25877) + INDEX</literal> on a Disk Data table did not always move data + from memory into the tablespace. (Bug #25877) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal> (Disk Data): When creating a @@ -290,23 +290,23 @@ nodes to crash. (Bug #25743) </para> </listitem> + <listitem> <para> <literal>NDB Cluster</literal>: It was not possible to set <literal>LockPagesInMainMemory</literal> equal to - <literal>0</literal>. (Bug #27291) + <literal>0</literal>. (Bug #27291) </para> </listitem> + <listitem> <para> - <literal>NDB Cluster</literal>: A race condition could sometimes occur if the node - acting as master failed while node IDs were still being - allocated during startup. (Bug #27286) + <literal>NDB Cluster</literal>: A race condition could + sometimes occur if the node acting as master failed while node + IDs were still being allocated during startup. (Bug #27286) </para> </listitem> - - - + <listitem> <para> <literal>NDB Cluster</literal>: When a data node was taking @@ -315,38 +315,38 @@ global checkpoints. (Bug #27283) </para> </listitem> - - - + <listitem> <para> - <literal>NDB Cluster</literal>: A delete operation using a scan following by an insert using - a scan could cause a data node to fail. (Bug #27203) + <literal>NDB Cluster</literal>: A delete operation using a + scan following by an insert using a scan could cause a data + node to fail. (Bug #27203) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal>: The same failed request from an API node could be handled by the cluster multiple times, - resulting in reduced performance. (Bug #27087) + resulting in reduced performance. (Bug #27087) </para> </listitem> - + <listitem> <para> - <literal>NDB Cluster</literal>: The failure of a data node while restarting could cause - other data nodes to hang or crash. (Bug #27003) + <literal>NDB Cluster</literal>: The failure of a data node + while restarting could cause other data nodes to hang or + crash. (Bug #27003) </para> </listitem> - + <listitem> <para> - <literal>NDB Cluster</literal>: <command>mysqld</command> processes would sometimes crash - under high load. (Bug #26825) + <literal>NDB Cluster</literal>: <command>mysqld</command> + processes would sometimes crash under high load. (Bug #26825) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal>: When performing an upgrade or @@ -355,12 +355,13 @@ upgrading management nodes. (Bug #21296) </para> </listitem> - + <listitem> <para> - <literal>NDB Cluster</literal>: Some values of <literal>MaxNoOfTables</literal> - caused the error <errortext>Job buffer congestion</errortext> - to occur. (Bug #19378) + <literal>NDB Cluster</literal>: Some values of + <literal>MaxNoOfTables</literal> caused the error + <errortext>Job buffer congestion</errortext> to occur. (Bug + #19378) </para> </listitem> @@ -1295,7 +1296,7 @@ Bug #24630, Bug#26556) </para> </listitem> - + <listitem> <para> <literal>NDB Cluster</literal> (APIs): After defining a delete @@ -1305,7 +1306,7 @@ <literal>BLOB</literal> or <literal>TEXT</literal> column, invoking <literal>NdbTransaction::execute()</literal> caused the calling application to enter an endless loop rather than - raising an error. (Bug #24028) + raising an error. (Bug #24028) </para> </listitem>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r5522 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 23 Mar |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.698 sec. using MySQL 5.1.14-beta-log