List:Commits« Previous MessageNext Message »
From:jon.stephens Date:November 24 2010 8:05pm
Subject:svn commit - mysqldoc@docsrva: r24001 - in trunk: dynamic-docs/changelog dynamic-docs/command-optvars refman-5.1
View as plain text  
Author: jstephens
Date: 2010-11-24 21:05:57 +0100 (Wed, 24 Nov 2010)
New Revision: 24001

Log:

Cluster BUG#58383 bugfix:

  Changelog entry

  TimeBetweenEpochsTimeout changes

  Implications for GCP stops, logging

Various minor fixes




Modified:
   trunk/dynamic-docs/changelog/mysqld-2.xml
   trunk/dynamic-docs/command-optvars/ndb-config-params.xml
   trunk/refman-5.1/mysql-cluster-configuration-core.xml
   trunk/refman-5.1/mysql-cluster-overview.xml


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2010-11-24 19:36:01 UTC (rev 24000)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2010-11-24 20:05:57 UTC (rev 24001)
Changed blocks: 1, Lines Added: 61, Lines Deleted: 0; 1945 bytes

@@ -11,6 +11,67 @@
     <tags>
       <highlight type="cluster"/>
       <highlight type="importantchange"/>
+      <manual type="TimeBetweenEpochsTimeout"/>
+      <manual type="GCP stop"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="58383"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.51-ndb-7.0.21"/>
+      <version ver="5.1.51-ndb-7.1.10"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The following changes have been made with regard to the
+        <literal role="ndbparam:ndbd">TimeBetweenEpochsTimeout</literal>
+        data node configuration parameter:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            The maximum possible value for this parameter has been
+            increased from 32000 milliseconds to 256000 milliseconds.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Setting this parameter to zero now disables the GCP monitor;
+            this has the effect of disabling GCP stops.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            The current value of this parameter and a warning are
+            written to the cluster log whenever a GCP save takes longer
+            than 1 minute or a GCP save takes longer than 10 seconds.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+      <para>
+        For more information, see
+        <xref linkend="mysql-cluster-ndbd-definition-gcp-stop-errors"/>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <tags>
+      <highlight type="cluster"/>
+      <highlight type="importantchange"/>
       <highlight type="innodb"/>
     </tags>
 


Modified: trunk/dynamic-docs/command-optvars/ndb-config-params.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/ndb-config-params.xml	2010-11-24 19:36:01 UTC (rev 24000)
+++ trunk/dynamic-docs/command-optvars/ndb-config-params.xml	2010-11-24 20:05:57 UTC (rev 24001)
Changed blocks: 1, Lines Added: 16, Lines Deleted: 0; 1212 bytes

@@ -4450,6 +4450,22 @@
       <value default="4000" minimum="0" maximum="32000"/>
     </values>
 
+    <values vartype="numeric" platform="all" units="milliseconds" outversion="5.1.51-ndb-7.0.20">
+      <value default="4000" minimum="0" maximum="32000"/>
+    </values>
+
+    <values vartype="numeric" platform="all" units="milliseconds" inversion="5.1.51-ndb-7.0.21">
+      <value default="4000" minimum="0" maximum="256000"/>
+    </values>
+
+    <values vartype="numeric" platform="all" units="milliseconds" outversion="5.1.51-ndb-7.1.9">
+      <value default="4000" minimum="0" maximum="32000"/>
+    </values>
+
+    <values vartype="numeric" platform="all" units="milliseconds" inversion="5.1.51-ndb-7.1.10">
+      <value default="4000" minimum="0" maximum="256000"/>
+    </values>
+
     <versions>
       <introduced version="5.1.22-ndb-6.2.7"/>
       <introduced version="5.1.22-ndb-6.3.4"/>


Modified: trunk/refman-5.1/mysql-cluster-configuration-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-configuration-core.xml	2010-11-24 19:36:01 UTC (rev 24000)
+++ trunk/refman-5.1/mysql-cluster-configuration-core.xml	2010-11-24 20:05:57 UTC (rev 24001)
Changed blocks: 4, Lines Added: 47, Lines Deleted: 6; 3230 bytes

@@ -4814,6 +4814,39 @@
             Cluster Replication. This parameter was introduced in MySQL
             Cluster NDB 6.2.7 and MySQL Cluster NDB 6.3.4.
           </para>
+
+          <para>
+            The following changes regarding this parameter were made in
+            MySQL Cluster NDB 7.0.21 and MySQL Cluster NDB 7.1.10:
+          </para>
+
+          <itemizedlist>
+
+            <listitem>
+              <para>
+                The maximum possible value for this parameter was
+                increased from 32000 milliseconds to 256000
+                milliseconds.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                Setting this parameter to zero now disables the GCP
+                monitor; this has the effect of disabling GCP stops.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                The current value of this parameter and a warning are
+                now written to the cluster log whenever a GCP save takes
+                longer than 1 minute or a GCP save takes longer than 10
+                seconds.
+              </para>
+            </listitem>
+
+          </itemizedlist>
         </listitem>
 
         <listitem>

@@ -7023,10 +7056,17 @@
 
       </itemizedlist>
 
+      <para>
+        Beginning with MySQL Cluster NDB 7.0.21 and MySQL Cluster NDB
+        7.0.10, it is possible to disable the GCP monitor by setting the
+        <literal role="ndbparam:ndbd">TimeBetweenEpochsTimeout</literal>
+        data node configuration parameter to 0.
+      </para>
+
       <formalpara>
 
         <title>Parameters for configuring send buffer memory allocation (MySQL Cluster
-          NDB 7.0)</title>
+          NDB 7.0 and later)</title>
 
         <para>
           Beginning with MySQL Cluster NDB 6.4.0, send buffer memory is

@@ -7132,11 +7172,11 @@
       <note>
         <para>
           Previous to MySQL Cluster NDB 7.0, to add new data nodes to a
-          MySQL Cluster, it is necessary to shut down the cluster
+          MySQL Cluster, it was necessary to shut down the cluster
           completely, update the <filename>config.ini</filename> file,
-          and then restart the cluster (that is, you must perform a
-          system restart). All data node processes must be started with
-          the <option>--initial</option> option.
+          and then restart the cluster (that is, you had to perform a
+          system restart). All data node processes had to be started
+          with the <option role="ndbd">--initial</option> option.
         </para>
 
         <para>

@@ -7219,7 +7259,8 @@
           <note>
             <para>
               This parameter is ignored unless
-              <literal>StartOnError</literal> is equal to 0.
+              <literal role="ndbparam:ndbd">StopOnError</literal> is
+              equal to 0.
             </para>
           </note>
         </listitem>


Modified: trunk/refman-5.1/mysql-cluster-overview.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-overview.xml	2010-11-24 19:36:01 UTC (rev 24000)
+++ trunk/refman-5.1/mysql-cluster-overview.xml	2010-11-24 20:05:57 UTC (rev 24001)
Changed blocks: 2, Lines Added: 44, Lines Deleted: 0; 2328 bytes

@@ -1846,6 +1846,28 @@
           </formalpara>
         </listitem>
 
+        <listitem>
+          <formalpara>
+
+            <title><literal>TimeBetweenEpochsTimeout</literal> and GCP stop control</title>
+
+            <para>
+              Beginning with MySQL Cluster NDB 7.1.10, it is possible to
+              disable GCP stops by setting
+              <literal role="ndbparam:ndbd">TimeBetweenEpochsTimeout</literal>
+              to 0. In addition, a warning is written to the cluster log
+              whenever the time required for a GCP save exceeds 60
+              seconds or the time required for a GCP commit exceeds 10
+              seconds. This warning includes a report of the current
+              value of
+              <literal role="ndbparam:ndbd">TimeBetweenEpochsTimeout</literal>.
+              For more information, see
+              <xref linkend="mysql-cluster-ndbd-definition-gcp-stop-errors"/>.
+            </para>
+
+          </formalpara>
+        </listitem>
+
       </itemizedlist>
 
       <para>

@@ -2736,6 +2758,28 @@
           </formalpara>
         </listitem>
 
+        <listitem>
+          <formalpara>
+
+            <title><literal>TimeBetweenEpochsTimeout</literal> and GCP stop control</title>
+
+            <para>
+              Beginning with MySQL Cluster NDB 7.0.21, it is possible to
+              disable GCP stops by setting
+              <literal role="ndbparam:ndbd">TimeBetweenEpochsTimeout</literal>
+              to 0. In addition, a warning is written to the cluster log
+              whenever the time required for a GCP save exceeds 60
+              seconds or the time required for a GCP commit exceeds 10
+              seconds. This warning includes a report of the current
+              value of
+              <literal role="ndbparam:ndbd">TimeBetweenEpochsTimeout</literal>.
+              For more information, see
+              <xref linkend="mysql-cluster-ndbd-definition-gcp-stop-errors"/>.
+            </para>
+
+          </formalpara>
+        </listitem>
+
       </itemizedlist>
 
       <para>


Thread
svn commit - mysqldoc@docsrva: r24001 - in trunk: dynamic-docs/changelog dynamic-docs/command-optvars refman-5.1jon.stephens24 Nov