Author: jstephens
Date: 2008-11-19 17:32:44 +0100 (Wed, 19 Nov 2008)
New Revision: 12542
Log:
Added changelog entry for Cluster Bug #40847 fix
Documented new InitFragmentLogFiles configuration parameter (Thanks,
Jonas!)
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/refman-5.1/mysql-cluster-configuration.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-11-19 16:14:50 UTC (rev 12541)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-11-19 16:32:44 UTC (rev 12542)
Changed blocks: 1, Lines Added: 30, Lines Deleted: 1; 1148 bytes
@@ -6,12 +6,41 @@
]>
<changelog>
- <logentry entrytype="bug">
+ <logentry entrytype="feature">
<tags>
+ <highlight type="cluster"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="40847"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.29-ndb-6.3.19"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When performing an initial start of a data node, fragment log
+ files were always created sparsely — that is, not all
+ bytes were written. Now it is possible to override this behavior
+ using the new <literal>InitFragmentLogFiles</literal>
+ configuration parameter.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="feature">
+
+ <tags>
<highlight type="clusterapi"/>
<manual type="mgmapi"/>
<manual type="errors"/>
+ <highlight type="importantchange"/>
</tags>
<bugs>
Modified: trunk/refman-5.1/mysql-cluster-configuration.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-configuration.xml 2008-11-19 16:14:50 UTC (rev 12541)
+++ trunk/refman-5.1/mysql-cluster-configuration.xml 2008-11-19 16:32:44 UTC (rev 12542)
Changed blocks: 2, Lines Added: 59, Lines Deleted: 0; 2867 bytes
@@ -2516,6 +2516,56 @@
<listitem>
<indexterm>
+ <primary>InitFragmentLogFiles</primary>
+ </indexterm>
+
+ <para id="mysql-cluster-param-ndbd-definition-initfragmentlogfiles">
+ <literal>InitFragmentLogFiles</literal>
+ </para>
+
+ <para>
+ By default, fragment log files are created sparsely when
+ performing an initial start of a data node — that is,
+ depending on the operating system and filesystem in use, not
+ all bytes are necessarily written to disk. Beginning with
+ MySQL Cluster NDB 6.3.19, it is possible to override this
+ behavior and force all bytes to be written regardless of the
+ platform and filesystem type being used by mean of this
+ parameter.
+ </para>
+
+ <para>
+ <literal>InitFragmentLogFiles</literal> takes one of two
+ values:
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>SPARSE</literal>. Fragment log files are
+ created sparsely. This is the default value.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>FULL</literal>. Force all bytes of the
+ fragment log file to be written to disk.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ <para>
+ Depending on your operating system and filesystem, setting
+ <literal>InitFragmentLogFiles=FULL</literal> may help
+ eliminate I/O errors on writes to the REDO log.
+ </para>
+ </listitem>
+
+ <listitem>
+ <indexterm>
<primary>MaxNoOfOpenFiles</primary>
</indexterm>
@@ -6070,6 +6120,15 @@
<entry>N</entry>
</row>
<row>
+ <entry><literal><link
linkend="mysql-cluster-param-ndbd-definition-initfragmentlogfiles">InitFragmentLogFiles</link></literal>
+ (Added in MySQL Cluster NDB 6.3.19)</entry>
+ <entry>string</entry>
+ <entry>full</entry>
+ <entry>sparse</entry>
+ <entry>sparse</entry>
+ <entry>IN</entry>
+ </row>
+ <row>
<entry><literal><link
linkend="mysql-cluster-param-ndbd-definition-initialnoofopenfiles">InitialNoOfOpenFiles</link></literal></entry>
<entry>integer</entry>
<entry>27</entry>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r12542 - in trunk: dynamic-docs/changelog refman-5.1 | jon | 19 Nov |