From: Date: November 19 2008 5:32pm Subject: svn commit - mysqldoc@docsrva: r12542 - in trunk: dynamic-docs/changelog refman-5.1 List-Archive: http://lists.mysql.com/commits/59250 Message-Id: <200811191632.mAJGWiLx022129@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 @@ ]> - + + + + + + + + + + + + + + + + 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 InitFragmentLogFiles + configuration parameter. + + + + + + + + + + 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 @@ + InitFragmentLogFiles + + + + InitFragmentLogFiles + + + + 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. + + + + InitFragmentLogFiles takes one of two + values: + + + + + + SPARSE. Fragment log files are + created sparsely. This is the default value. + + + + + + FULL. Force all bytes of the + fragment log file to be written to disk. + + + + + + + + Depending on your operating system and filesystem, setting + InitFragmentLogFiles=FULL may help + eliminate I/O errors on writes to the REDO log. + + + + + MaxNoOfOpenFiles @@ -6070,6 +6120,15 @@ N + InitFragmentLogFiles + (Added in MySQL Cluster NDB 6.3.19) + string + full + sparse + sparse + IN + + InitialNoOfOpenFiles integer 27