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.3 NDB Cluster SQL Node and API Node Configuration Parameters

Contents

The listing in this section provides information about parameters used in the [mysqld] and [api] sections of a config.ini file for configuring NDB Cluster SQL nodes and API nodes. For detailed descriptions and other additional information about each of these parameters, see Section 22.3.3.7, “Defining SQL and Other API Nodes in an NDB Cluster”.

  • ApiVerbose: Enable NDB API debugging; for NDB development

  • ArbitrationDelay: When asked to arbitrate, arbitrator waits this many milliseconds before voting

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

  • AutoReconnect: Specifies whether an API node should reconnect fully when disconnected from the cluster

  • BatchByteSize: The default batch size in bytes

  • BatchSize: The default batch size in number of records

  • ConnectBackoffMaxTime: Specifies longest time in milliseconds (~100ms resolution) to allow between connection attempts to any given data node by this API node. Excludes time elapsed while connection attempts are ongoing, which in worst case can take several seconds. Disable by setting to 0. If no data nodes are currently connected to this API node, StartConnectBackoffMaxTime is used instead.

  • ConnectionMap: Specifies which data nodes to connect

  • DefaultHashMapSize: Set size (in buckets) to use for table hash maps. Three values are supported: 0, 240, and 3840. Intended primarily for upgrades and downgrades within NDB 7.2.

  • DefaultOperationRedoProblemAction: How operations are handled in the event that RedoOverCommitCounter is exceeded

  • 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.

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

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

  • Id: Number identifying MySQL server or API node (Id). Now deprecated; use NodeId instead.

  • MaxScanBatchSize: The maximum collective batch size for one scan

  • NodeId: Number uniquely identifying the SQL node or API node among all nodes in the cluster.

  • StartConnectBackoffMaxTime: Same as ConnectBackoffMaxTime except that this parameter is used in its place if no data nodes are connected to this API node.

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

  • wan: Use WAN TCP setting as default

For a discussion of MySQL server options for NDB Cluster, see Section 22.3.3.9.1, “MySQL Server Options for NDB Cluster”. For information about MySQL server system variables relating to NDB Cluster, see Section 22.3.3.9.2, “NDB Cluster System Variables”.

Note

To add new SQL or API nodes to the configuration of a running NDB Cluster, it is necessary to perform a rolling restart of all cluster nodes after adding new [mysqld] or [api] sections to the config.ini file (or files, if you are using more than one management server). This must be done before the new SQL or API nodes can connect to the cluster.

It is not necessary to perform any restart of the cluster if new SQL or API nodes can employ previously unused API slots in the cluster configuration to connect to the cluster.


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-api.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