No cache version.


Caching disabled. Default setting for this page:enabled (code DEF204)
If the display is too slow, you can disable the user mode to view the cached version.

Rechercher dans le manuel MySQL

22.3.2.2 NDB Cluster Management Node Configuration Parameters

Contents

The listing in this section provides information about parameters used in the [ndb_mgmd] or [mgm] section of a config.ini file for configuring NDB Cluster management nodes. For detailed descriptions and other additional information about each of these parameters, see Section 22.3.3.5, “Defining an NDB Cluster Management Server”.

  • ArbitrationDelay: When asked to arbitrate, arbitrator waits this long before voting (milliseconds)

  • ArbitrationRank: If 0, then management node is not arbitrator. Kernel selects arbitrators in order 1, 2

  • DataDir: Data directory for this node

  • ExecuteOnComputer: String referencing an earlier defined COMPUTER

  • ExtraSendBufferMemory: Memory to use for send buffers in addition to any allocated by TotalSendBufferMemory or SendBufferMemory. Default (0) allows up to 16MB.

  • HeartbeatIntervalMgmdMgmd: Time between management node-to-management node heartbeats; the connection between management node is considered lost after 3 missed heartbeats.

  • HeartbeatThreadPriority: Set heartbeat thread policy and priority for management nodes; see manual for allowed values

  • HostName: Host name or IP address for this management node.

  • Id: Number identifying the management node (Id). Now deprecated; use NodeId instead.

  • LogDestination: Where to send log messages: console, system log, or specified log file

  • NodeId: Number uniquely identifying the management node among all nodes in the cluster.

  • PortNumber: Port number to send commands to and fetch configuration from management server

  • PortNumberStats: Port number used to get statistical information from a management server

  • TotalSendBufferMemory: Total memory to use for all transporter send buffers

  • wan: Use WAN TCP setting as default

Note

After making changes in a management node's configuration, it is necessary to perform a rolling restart of the cluster for the new configuration to take effect. See Section 22.3.3.5, “Defining an NDB Cluster Management Server”, for more information.

To add new management servers to a running NDB Cluster, it is also necessary perform a rolling restart of all cluster nodes after modifying any existing config.ini files. For more information about issues arising when using multiple management nodes, see Section 22.1.7.10, “Limitations Relating to Multiple NDB Cluster Nodes”.


Find a PHP function

Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-mysql-cluster-params-mgmd.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:en Manuel MySQL : https://dev.mysql.com/

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut