Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Install...urce_tree.html

ChangeSet
1.2608 05/02/25 20:10:55 jon (AT) gigan (DOT) homedns.org +1 -0
Cluster: NDB_MGMD is now preferred over
MGM for use in config files (per Tomas).

Docs/manual.texi
1.2426 05/02/25 20:10:51 jon (AT) gigan (DOT) homedns.org +13 -12
Cluster: NDB_MGMD is now preferred over
MGM for use in config files (per Tomas).

# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: jon
# Host: gigan.site
# Root: /home/jon/bk/mysqldoc

--- 1.2425/Docs/manual.texi 2005-02-25 20:03:32 +10:00
+++ 1.2426/Docs/manual.texi 2005-02-25 20:10:51 +10:00
@@ -71574,25 +71574,25 @@
@node MySQL Cluster MGM Definition, MySQL Cluster DB Definition, MySQL Cluster Computer Definition, MySQL Cluster Config File
@subsubsection Defining the MySQL Cluster Management Server

-The @code{[MGM]} section (or its alias @code{[NDB_MGMD]}) is used to configure
+The @code{[NDB_MGMD]} section (or its alias @code{[MGM]}) is used to configure
the behaviour of the management server. Either the @code{ExecuteOnComputer} or
@code{HostName} parameter must be present. All other parameters in the
following can be omitted and, if so, will assume their default values.

@table @code
-@item [MGM]Id
+@item [NDB_MGMD]Id
Each node in the cluster has a unique identity, which is represented by an
integer value in the range 1 - 63 inclusive. This ID is used by all internal
cluster messages for addressing the node.

-@item [MGM]ExecuteOnComputer
+@item [NDB_MGMD]ExecuteOnComputer
This refers to one of the computers defined in the @code{[COMPUTER]} section.

-@item [MGM]PortNumber
+@item [NDB_MGMD]PortNumber
This is the port number on which the management server listens for configuration
requests and management commands.

-@item [MGM]LogDestination
+@item [NDB_MGMD]LogDestination
This parameter specifies where to send cluster logging information. There are
three options in this regard: @code{CONSOLE}, @code{SYSLOG}, and @code{FILE}:

@@ -71656,7 +71656,7 @@

@end itemize

-@item [MGM]ArbitrationRank
+@item [NDB_MGMD]ArbitrationRank
This parameter is used to define which nodes can act as arbitrators. Only MGM
nodes and SQL nodes can be arbitrators. @code{ArbitrationRank} can take one of
the following values:
@@ -71680,17 +71680,17 @@
setting its @code{ArbitrationRank} to 1 (the default value) and that of all SQL
nodes to 0.

-@item [MGM]ArbitrationDelay
+@item [NDB_MGMD]ArbitrationDelay
An integer value which causes the management server's responses to
arbitration requests to be delayed by that number of milliseconds.
By default, this value is 0; it is normally not necessary to change it.

-@item [MGM]DataDir
+@item [NDB_MGMD]DataDir
This sets the directory where output files from the management server
will be placed. These files include cluster log files, process output
files, and the daemon's pid file. (For log files, this can be
overridden by setting the @code{FILE} parameter for
-@code{[MGM]LogDestination} as discussed previously in this section.)
+@code{[NDB_MGMD]LogDestination} as discussed previously in this section.)

@end table

@@ -71698,8 +71698,6 @@
@node MySQL Cluster DB Definition, MySQL Cluster API Definition, MySQL Cluster MGM Definition, MySQL Cluster Config File
@subsubsection Defining MySQL Cluster Storage Nodes

-@c TODO: Add section headings
-
The @code{[NDBD]} section is used to configure the behavior of the storage
nodes. There are many parameters which control buffer sizes, pool
sizes, timeouts, and so forth. The only mandatory parameters are:
@@ -112475,7 +112473,10 @@
@item
In the configuration file, you can now use @code{[NDBD]} as an alias for
@code{[DB]}, @code{[MYSQLD]} as an alias for @code{[API]}, and
-@code{[NDB_MGMD]} as an alias for @code{[MGM]}.
+@code{[NDB_MGMD]} as an alias for @code{[MGM]}. @strong{Note}: @code{[NDBD]},
+@code{[MYSQLD]}, and @code{[NDB_MGMD]} are now the preferred designations,
+although the older ones will continue to be supported for some time in order to
+provide backwards compatibility.

@item
Many more checks of the consistency of the configuration have been

--
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe: http://lists.mysql.com/internals?uns...ie.nctu.edu.tw