Rolling restarts with multiple management servers-opracowanie

Rolling restarts with multiple management servers. When performing a rolling restart of a
MySQL Cluster with multiple management nodes, you should keep in mind that ndb_mgmd checks to
see if any other management node is running, and, if so, tries to use that node's configuration data. To
keep this from occurring, and to force ndb_mgmd to reread its configuration file, perform the following
steps:
1. Stop all MySQL Cluster ndb_mgmd processes.
2. Update all config.ini files.
3. Start a single ndb_mgmd with --reload [2342], --initial [2341], or both options as desired.
4. If you started the first ndb_mgmd with the --initial [2341] option, you must also start any
remaining ndb_mgmd processes using --initial.
Regardless of any other options used when starting the first ndb_mgmd, you should not start any
remaining ndb_mgmd processes after the first one using --reload [2342].
5. Complete the rolling restarts of the data nodes and API nodes as normal.
When performing a rolling restart to update the cluster's configuration, you can use the
config_generation column of the ndbinfo.nodes table to keep track of which data nodes have
been successfully restarted with the new configuration. See Section 17.5.10.13, “The ndbinfo nodes
Table”.
... zobacz całą notatkę