MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon.stephens Date:September 9 2010 6:41am
Subject:svn commit - mysqldoc@docsrva: r22632 - trunk/refman-5.1
View as plain text  
Author: jstephens
Date: 2010-09-09 08:41:54 +0200 (Thu, 09 Sep 2010)
New Revision: 22632


Fixes Docs BUG#56229 (--skip-config-cache doesn't disable 
configuration caching if cache files already exist)


Modified: trunk/refman-5.1/mysql-cluster-programs-core.xml
--- trunk/refman-5.1/mysql-cluster-programs-core.xml	2010-09-08 20:07:39 UTC (rev 22631)
+++ trunk/refman-5.1/mysql-cluster-programs-core.xml	2010-09-09 06:41:54 UTC (rev 22632)
Changed blocks: 4, Lines Added: 65, Lines Deleted: 6; 5036 bytes

@@ -1800,9 +1800,68 @@
+              Using one of the options just listed is effective only if
+              the management server has no stored configuration at the
+              time it is started. If the management server finds any
+              configuration cache files, then the
+              <option>--config-cache</option> option or the
+              <option>--skip-config-cache</option> option is ignored.
+              Therefore, to disable configuration caching, the option
+              should be used the <emphasis>first</emphasis> time that
+              the management server is started. Otherwise&mdash;that is,
+              if you wish to disable configuration caching for a
+              management server that has <emphasis>already</emphasis>
+              created a configuration cache&mdash;you must stop the
+              management server, delete any existing configuration cache
+              files manually, then restart the management server with
+              <option>--skip-config-cache</option> (or with
+              <option>--config-cache</option> set equal to 0,
+              <literal>OFF</literal>, or <literal>FALSE</literal>).
+            </para>
+            <para>
+              Configuration cache files are normally created in a
+              directory named <filename>mysql-cluster</filename> under
+              the installation directory (unless this location has been
+              overridden using the
+              <option role="ndb_mgmd">--configdir</option> option). Each
+              time the management server updates its configuration data,
+              it writes a new cache file. The files are named
+              sequentially in order of creation using the following
+              format:
+            </para>
+            <para>
+              <replaceable>node-id</replaceable> is the management
+              server&apos;s node ID;
+              <replaceable>seq-number</replaceable> is a sequence
+              number, beginning with 1. For example, if the management
+              server&apos;s node ID is 5, then the first three
+              configuration cache files would, when they are created, be
+              named <filename>ndb_5_config.bin.1</filename>,
+              <filename>ndb_5_config.bin.2</filename>, and
+              <filename>ndb_5_config.bin.3</filename>.
+            </para>
+            <para>
+              If your intent is to purge or reload the configuration
+              cache without actually disabling caching, you should start
+              <command>ndb_mgmd</command> with one of the options
+              <option role="ndb_mgmd">--reload</option> or
+              <option role="ndb_mgmd">--initial</option> instead of
+              <option>--skip-config-cache</option>.
+            </para>
+            <para>
               To re-enable the configuration cache, simply restart the
-              management server, without the
-              <option>--config-cache</option> option.
+              management server, but without the
+              <option>--config-cache</option> or
+              <option>--skip-config-cache</option> option that was used
+              previously to disable the configuration cache.

@@ -1908,7 +1967,7 @@
               This differs in two ways from the
-              <option>--reload</option> option. First,
+              <option role="ndb_mgmd">--reload</option> option. First,
               <option>--reload</option> forces the server to check the
               configuration file against the cache and reload its data
               only if the contents of the file are different from the

@@ -1994,8 +2053,8 @@
               about the cluster setup including an extensive list of the
               cluster configuration sections as well as parameters and
               their values. Normally used together with the
-              <option>--config-file</option> (<option>-f</option>)
-              option.
+              <option role="ndb_mgmd">--config-file</option>
+              (<option>-f</option>) option.

@@ -2025,7 +2084,7 @@
               This differs in two ways from the
-              <option>--initial</option> option. First,
+              <option role="ndb_mgmd">--initial</option> option. First,
               <option>--initial</option> causes all cache files to be
               deleted. Second, <option>--initial</option> forces the
               management server to re-read the global configuration file

svn commit - mysqldoc@docsrva: r22632 - trunk/refman-5.1jon.stephens9 Sep