| List: | Commits | « Previous MessageNext Message » | |
| From: | jon | Date: | May 2 2006 2:30pm |
| Subject: | svn commit - mysqldoc@docsrva: r1990 - in trunk: refman-4.1 refman-5.0 refman-5.1 | ||
| View as plain text | |||
Author: jstephens Date: 2006-05-02 14:30:21 +0200 (Tue, 02 May 2006) New Revision: 1990 Log: Reformat. Modified: trunk/refman-4.1/ndbcluster.xml trunk/refman-5.0/ndbcluster.xml trunk/refman-5.1/ndbcluster.xml Modified: trunk/refman-4.1/ndbcluster.xml =================================================================== --- trunk/refman-4.1/ndbcluster.xml 2006-05-02 12:29:01 UTC (rev 1989) +++ trunk/refman-4.1/ndbcluster.xml 2006-05-02 12:30:21 UTC (rev 1990) @@ -423,7 +423,7 @@ <para> <emphasis role="bold">Node Group</emphasis>: A node group consists of one or more nodes, and stores partitions, or - sets of <firstterm>replicas</firstterm> (see next item). + sets of <firstterm>replicas</firstterm> (see next item). </para> <para> @@ -436,15 +436,15 @@ <para> <emphasis role="bold">Partition</emphasis>: This is a portion of the data stored by the cluster. There are as many - cluster partitions as nodes participating in the - cluster. Each node is responible for keeping at least one - copy of any partitions assigned to it (that is, at least one - replica) available to the cluster. + cluster partitions as nodes participating in the cluster. + Each node is responible for keeping at least one copy of any + partitions assigned to it (that is, at least one replica) + available to the cluster. </para> <para> - A replica belongs entirely to a single node; a node can - (and usually does) store several replicas. + A replica belongs entirely to a single node; a node can (and + usually does) store several replicas. </para> </listitem> @@ -466,7 +466,7 @@ and 2 belong to node group 0, and nodes 3 and 4 belong to node group 1. Note that only data (<command>ndbd</command>) nodes are shown here; although a working cluster requires an - <command>ndb_mgm</command> process for cluster management and at + <command>ndb_mgm</command> process for cluster management and at least one SQL node to access the data stored by the cluster, these have been omitted in the figure for clarity. </para> @@ -485,20 +485,20 @@ The data stored by the cluster is divided into four partitions, numbered 0, 1, 2, and 3. Each partition is stored — in multiple copies — on the same node group. Partitions are - stored on alternate node groups: - Partition 2 is stored on . + stored on alternate node groups: Partition 2 is stored on . </para> - + <itemizedlist> + <listitem> <para> Partition 0 is stored on node group 0; a <firstterm>primary - replica</firstterm> (primary copy) is stored on node 1, - and a <firstterm>backup replica</firstterm> (backup copy of - the partition) is stored on node 2. + replica</firstterm> (primary copy) is stored on node 1, and + a <firstterm>backup replica</firstterm> (backup copy of the + partition) is stored on node 2. </para> </listitem> - + <listitem> <para> Partition 1 is stored on the other node group (node group @@ -506,7 +506,7 @@ backup replica is on node 4. </para> </listitem> - + <listitem> <para> Partition 2 is stored on node group 0. However, the placing @@ -515,7 +515,7 @@ and the backup on node 1. </para> </listitem> - + <listitem> <para> Partition 3 is stored on node group 1, and the placement of @@ -524,9 +524,9 @@ backup on node 3. </para> </listitem> + </itemizedlist> - - + <para> What this means so far as the continued operation of a MySQL Cluster is this: so long as each node group participating in the @@ -552,8 +552,8 @@ <para> In this example, where the cluster consists of two node groups of two nodes each, any combination of at least one node in node - group 0 and at least one node in node group 1 is sufficient - to keep the cluster <quote>alive</quote> (indicated by arrows in + group 0 and at least one node in node group 1 is sufficient to + keep the cluster <quote>alive</quote> (indicated by arrows in the diagram). However, if <emphasis>both</emphasis> nodes from <emphasis>either</emphasis> node group fail, the remaining two nodes are not sufficient (shown by the arrows marked out with an @@ -1984,10 +1984,10 @@ </programlisting> <para> - Then start a single data node by running <command>ndbd</command>. - When starting <command>ndbd</command> for a given data node for - the very first time, you should use the - <option>--initial</option> option as shown here: + Then start a single data node by running + <command>ndbd</command>. When starting <command>ndbd</command> + for a given data node for the very first time, you should use + the <option>--initial</option> option as shown here: </para> <programlisting> @@ -2291,7 +2291,7 @@ <para> For additional <literal>NDB</literal> variables that can be - set in the <filename>my.cnf</filename> file, see + set in the <filename>my.cnf</filename> file, see <xref linkend="server-system-variables"/>. </para> @@ -10904,7 +10904,7 @@ </para> <para> - ( We implemented disk data storage for MySQL Cluster in MySQL + ( We implemented disk data storage for MySQL Cluster in MySQL 5.1, but we have no plans to add this capability in MySQL ¤t-series;.) </para> @@ -11925,9 +11925,9 @@ <emphasis role="bold">Note Regarding Terms</emphasis>: In older versions of the MySQL Cluster documentation, data nodes were sometimes referred to as <quote>database nodes</quote> or - <quote>data nodes</quote>. The term <quote>storage nodes</quote> - has also been used. In addition, SQL nodes were sometimes - known as <quote>client nodes</quote> or <quote>API + <quote>data nodes</quote>. The term <quote>storage + nodes</quote> has also been used. In addition, SQL nodes were + sometimes known as <quote>client nodes</quote> or <quote>API nodes</quote>. This older terminology has been deprecated to minimize confusion, and for these reasons should be avoided. </para> Modified: trunk/refman-5.0/ndbcluster.xml =================================================================== --- trunk/refman-5.0/ndbcluster.xml 2006-05-02 12:29:01 UTC (rev 1989) +++ trunk/refman-5.0/ndbcluster.xml 2006-05-02 12:30:21 UTC (rev 1990) @@ -423,7 +423,7 @@ <para> <emphasis role="bold">Node Group</emphasis>: A node group consists of one or more nodes, and stores partitions, or - sets of <firstterm>replicas</firstterm> (see next item). + sets of <firstterm>replicas</firstterm> (see next item). </para> <para> @@ -436,15 +436,15 @@ <para> <emphasis role="bold">Partition</emphasis>: This is a portion of the data stored by the cluster. There are as many - cluster partitions as nodes participating in the - cluster. Each node is responible for keeping at least one - copy of any partitions assigned to it (that is, at least one - replica) available to the cluster. + cluster partitions as nodes participating in the cluster. + Each node is responible for keeping at least one copy of any + partitions assigned to it (that is, at least one replica) + available to the cluster. </para> <para> - A replica belongs entirely to a single node; a node can - (and usually does) store several replicas. + A replica belongs entirely to a single node; a node can (and + usually does) store several replicas. </para> </listitem> @@ -466,7 +466,7 @@ and 2 belong to node group 0, and nodes 3 and 4 belong to node group 1. Note that only data (<command>ndbd</command>) nodes are shown here; although a working cluster requires an - <command>ndb_mgm</command> process for cluster management and at + <command>ndb_mgm</command> process for cluster management and at least one SQL node to access the data stored by the cluster, these have been omitted in the figure for clarity. </para> @@ -485,20 +485,20 @@ The data stored by the cluster is divided into four partitions, numbered 0, 1, 2, and 3. Each partition is stored — in multiple copies — on the same node group. Partitions are - stored on alternate node groups: - Partition 2 is stored on . + stored on alternate node groups: Partition 2 is stored on . </para> - + <itemizedlist> + <listitem> <para> Partition 0 is stored on node group 0; a <firstterm>primary - replica</firstterm> (primary copy) is stored on node 1, - and a <firstterm>backup replica</firstterm> (backup copy of - the partition) is stored on node 2. + replica</firstterm> (primary copy) is stored on node 1, and + a <firstterm>backup replica</firstterm> (backup copy of the + partition) is stored on node 2. </para> </listitem> - + <listitem> <para> Partition 1 is stored on the other node group (node group @@ -506,7 +506,7 @@ backup replica is on node 4. </para> </listitem> - + <listitem> <para> Partition 2 is stored on node group 0. However, the placing @@ -515,7 +515,7 @@ and the backup on node 1. </para> </listitem> - + <listitem> <para> Partition 3 is stored on node group 1, and the placement of @@ -524,9 +524,9 @@ backup on node 3. </para> </listitem> + </itemizedlist> - - + <para> What this means so far as the continued operation of a MySQL Cluster is this: so long as each node group participating in the @@ -552,8 +552,8 @@ <para> In this example, where the cluster consists of two node groups of two nodes each, any combination of at least one node in node - group 0 and at least one node in node group 1 is sufficient - to keep the cluster <quote>alive</quote> (indicated by arrows in + group 0 and at least one node in node group 1 is sufficient to + keep the cluster <quote>alive</quote> (indicated by arrows in the diagram). However, if <emphasis>both</emphasis> nodes from <emphasis>either</emphasis> node group fail, the remaining two nodes are not sufficient (shown by the arrows marked out with an @@ -1986,10 +1986,10 @@ </programlisting> <para> - Then start a single data node by running <command>ndbd</command>. - When starting <command>ndbd</command> for a given data node for - the very first time, you should use the - <option>--initial</option> option as shown here: + Then start a single data node by running + <command>ndbd</command>. When starting <command>ndbd</command> + for a given data node for the very first time, you should use + the <option>--initial</option> option as shown here: </para> <programlisting> @@ -2281,7 +2281,7 @@ <para> For additional <literal>NDB</literal> variables that can be - set in the <filename>my.cnf</filename> file, see + set in the <filename>my.cnf</filename> file, see <xref linkend="server-system-variables"/>. </para> @@ -7653,12 +7653,12 @@ Starts the data node identified by <replaceable>node_id</replaceable> (or all data nodes). </para> - + <para> Beginning with MySQL 5.0.19, this command can also be used - to start individual management nodes. + to start individual management nodes. <emphasis role="bold">Note</emphasis>: <literal>ALL - START</literal> continues to affect data nodes only. + START</literal> continues to affect data nodes only. </para> </listitem> @@ -7671,12 +7671,12 @@ Stops the data node identified by <replaceable>node_id</replaceable> (or all data nodes). </para> - + <para> Beginning with MySQL 5.0.19, this command can also be used - to stop individual management nodes. + to stop individual management nodes. <emphasis role="bold">Note</emphasis>: <literal>ALL - STOP</literal> continues to affect data nodes only. + STOP</literal> continues to affect data nodes only. </para> </listitem> @@ -11203,7 +11203,7 @@ </para> <para> - ( We implemented disk data storage for MySQL Cluster in MySQL + ( We implemented disk data storage for MySQL Cluster in MySQL 5.1, but we have no plans to add this capability in MySQL ¤t-series;.) </para> @@ -12233,9 +12233,9 @@ <emphasis role="bold">Note Regarding Terms</emphasis>: In older versions of the MySQL Cluster documentation, data nodes were sometimes referred to as <quote>database nodes</quote> or - <quote>data nodes</quote>. The term <quote>storage nodes</quote> - has also been used. In addition, SQL nodes were sometimes - known as <quote>client nodes</quote> or <quote>API + <quote>data nodes</quote>. The term <quote>storage + nodes</quote> has also been used. In addition, SQL nodes were + sometimes known as <quote>client nodes</quote> or <quote>API nodes</quote>. This older terminology has been deprecated to minimize confusion, and for these reasons should be avoided. </para> Modified: trunk/refman-5.1/ndbcluster.xml =================================================================== --- trunk/refman-5.1/ndbcluster.xml 2006-05-02 12:29:01 UTC (rev 1989) +++ trunk/refman-5.1/ndbcluster.xml 2006-05-02 12:30:21 UTC (rev 1990) @@ -420,7 +420,7 @@ <para> <emphasis role="bold">Node Group</emphasis>: A node group consists of one or more nodes, and stores partitions, or - sets of <firstterm>replicas</firstterm> (see next item). + sets of <firstterm>replicas</firstterm> (see next item). </para> <para> @@ -433,15 +433,15 @@ <para> <emphasis role="bold">Partition</emphasis>: This is a portion of the data stored by the cluster. There are as many - cluster partitions as nodes participating in the - cluster. Each node is responible for keeping at least one - copy of any partitions assigned to it (that is, at least one - replica) available to the cluster. + cluster partitions as nodes participating in the cluster. + Each node is responible for keeping at least one copy of any + partitions assigned to it (that is, at least one replica) + available to the cluster. </para> <para> - A replica belongs entirely to a single node; a node can - (and usually does) store several replicas. + A replica belongs entirely to a single node; a node can (and + usually does) store several replicas. </para> </listitem> @@ -463,7 +463,7 @@ and 2 belong to node group 0, and nodes 3 and 4 belong to node group 1. Note that only data (<command>ndbd</command>) nodes are shown here; although a working cluster requires an - <command>ndb_mgm</command> process for cluster management and at + <command>ndb_mgm</command> process for cluster management and at least one SQL node to access the data stored by the cluster, these have been omitted in the figure for clarity. </para> @@ -482,20 +482,20 @@ The data stored by the cluster is divided into four partitions, numbered 0, 1, 2, and 3. Each partition is stored — in multiple copies — on the same node group. Partitions are - stored on alternate node groups: - Partition 2 is stored on . + stored on alternate node groups: Partition 2 is stored on . </para> - + <itemizedlist> + <listitem> <para> Partition 0 is stored on node group 0; a <firstterm>primary - replica</firstterm> (primary copy) is stored on node 1, - and a <firstterm>backup replica</firstterm> (backup copy of - the partition) is stored on node 2. + replica</firstterm> (primary copy) is stored on node 1, and + a <firstterm>backup replica</firstterm> (backup copy of the + partition) is stored on node 2. </para> </listitem> - + <listitem> <para> Partition 1 is stored on the other node group (node group @@ -503,7 +503,7 @@ backup replica is on node 4. </para> </listitem> - + <listitem> <para> Partition 2 is stored on node group 0. However, the placing @@ -512,7 +512,7 @@ and the backup on node 1. </para> </listitem> - + <listitem> <para> Partition 3 is stored on node group 1, and the placement of @@ -521,9 +521,9 @@ backup on node 3. </para> </listitem> + </itemizedlist> - - + <para> What this means so far as the continued operation of a MySQL Cluster is this: so long as each node group participating in the @@ -549,8 +549,8 @@ <para> In this example, where the cluster consists of two node groups of two nodes each, any combination of at least one node in node - group 0 and at least one node in node group 1 is sufficient - to keep the cluster <quote>alive</quote> (indicated by arrows in + group 0 and at least one node in node group 1 is sufficient to + keep the cluster <quote>alive</quote> (indicated by arrows in the diagram). However, if <emphasis>both</emphasis> nodes from <emphasis>either</emphasis> node group fail, the remaining two nodes are not sufficient (shown by the arrows marked out with an @@ -1968,10 +1968,10 @@ </programlisting> <para> - Then start a single data node by running <command>ndbd</command>. - When starting <command>ndbd</command> for a given data node for - the very first time, you should use the - <option>--initial</option> option as shown here: + Then start a single data node by running + <command>ndbd</command>. When starting <command>ndbd</command> + for a given data node for the very first time, you should use + the <option>--initial</option> option as shown here: </para> <programlisting> @@ -2263,7 +2263,7 @@ <para> For additional <literal>NDB</literal> variables that can be - set in the <filename>my.cnf</filename> file, see + set in the <filename>my.cnf</filename> file, see <xref linkend="server-system-variables"/>. </para> @@ -7506,8 +7506,8 @@ <para> Starts the data or management node identified by <replaceable>node_id</replaceable>. Note that <literal>ALL - START</literal> works to start all data nodes only, and - does not affect management nodes. + START</literal> works to start all data nodes only, and does + not affect management nodes. </para> </listitem> @@ -7519,8 +7519,8 @@ <para> Starts the data or management node identified by <replaceable>node_id</replaceable>. Note that <literal>ALL - STOP</literal> works to start all data nodes only, and - does not affect management nodes. + STOP</literal> works to start all data nodes only, and does + not affect management nodes. </para> </listitem> @@ -14299,9 +14299,9 @@ <emphasis role="bold">Note Regarding Terms</emphasis>: In older versions of the MySQL Cluster documentation, data nodes were sometimes referred to as <quote>database nodes</quote> or - <quote>data nodes</quote>. The term <quote>storage nodes</quote> - has also been used. In addition, SQL nodes were sometimes - known as <quote>client nodes</quote> or <quote>API + <quote>data nodes</quote>. The term <quote>storage + nodes</quote> has also been used. In addition, SQL nodes were + sometimes known as <quote>client nodes</quote> or <quote>API nodes</quote>. This older terminology has been deprecated to minimize confusion, and for these reasons should be avoided. </para>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r1990 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 2 May |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.697 sec. using MySQL 5.1.14-beta-log