Rechercher dans le manuel MySQL
22.3.2.3 NDB Cluster SQL Node and API Node Configuration Parameters
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 developmentArbitrationDelay
: When asked to arbitrate, arbitrator waits this many milliseconds before votingArbitrationRank
: If 0, then API node is not arbitrator. Kernel selects arbitrators in order 1, 2AutoReconnect
: Specifies whether an API node should reconnect fully when disconnected from the clusterBatchByteSize
: The default batch size in bytesBatchSize
: The default batch size in number of recordsConnectBackoffMaxTime
: 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 connectDefaultHashMapSize
: 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 exceededExecuteOnComputer
: String referencing an earlier defined COMPUTERExtraSendBufferMemory
: 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 valuesHostName
: 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 scanNodeId
: 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 bufferswan
: 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”.
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.
Traduction non disponible
Le manuel MySQL n'est pas encore traduit en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.
Document créé le 26/06/2006, dernière modification le 26/10/2018
Source du document imprimé : https://www.gaudry.be/mysql-rf-mysql-cluster-params-api.html
L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.
Références
Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.