MySQL Cluster Configuration Files
1584
For queries that are translated into full table scans or range scans on indexes, it is important for best
performance to fetch records in properly sized batches. It is possible to set the proper size both in
terms of number of records (
BatchSize
) and in terms of bytes (
BatchByteSize
). The actual batch
size is limited by both parameters.
The speed at which queries are performed can vary by more than 40% depending upon how this
parameter is set. In future releases, MySQL Server will make educated guesses on how to set
parameters relating to batch size, based on the query type.
This parameter is measured in bytes and by default is equal to 32KB.
•
BatchSize
Effective Version
Type/Units
Default
Range/Values
MySQL 5.0.0
records
64
1 - 992
Restart Type: N
This parameter is measured in number of records and is by default set to 64. The maximum size is
992.
•
MaxScanBatchSize
Effective Version
Type/Units
Default
Range/Values
MySQL 5.0.0
bytes
256K
32K - 16M
Restart Type: N
The batch size is the size of each batch sent from each data node. Most scans are performed in
parallel to protect the MySQL Server from receiving too much data from many nodes in parallel; this
parameter sets a limit to the total batch size over all nodes.
The default value of this parameter is set to 256KB. Its maximum size is 16MB.
You can obtain some information from a MySQL server running as a Cluster SQL node using
SHOW
STATUS
in the
mysql
client, as shown here:
mysql>
SHOW STATUS LIKE 'ndb%';
+-----------------------------+---------------+
| Variable_name | Value |
+-----------------------------+---------------+
| Ndb_cluster_node_id | 5 |
| Ndb_config_from_host | 192.168.0.112 |
| Ndb_config_from_port | 1186 |
| Ndb_number_of_storage_nodes | 4 |
+-----------------------------+---------------+
4 rows in set (0.02 sec)
For information about these Cluster system status variables, see
Section 5.1.6, “Server Status
Variables”
.
Note
To add new SQL or API nodes to the configuration of a running MySQL 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.
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...