Datanode parameter MaxNoofConcurrentOperation analysis _ MySQL

Analysis of the datanode parameter MaxNoofConcurrentOperation on Opera

BitsCN.com

Analysis of the data node parameter MaxNoofConcurrentOperation

After the database is initialized, we will import data to the table in

# Mysql-u mysql-p myro_cluster

ERROR 1297 (HY000) at line 8: Got temporary err 233 'out of operation records in transaction coordinator (increase MaxNoofConcurrentOperation) 'from NDBCLUSTER.

Data node parameter MaxNoofConcurrentOperation: range: 32 K ~ 4G. The default value is 32 K.

Principle: adjust the value of this parameter based on the number and size of transactions. If you execute a large transaction and introduce a large number of records, you need to set this value to a greater value.

For specific value settings, see the link: http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-ndbd-definition.html#ndbparam-ndbd-maxnoofconcurrentoperations

Transactions are proposed to ensure data consistency, mainly for concurrent operations, because concurrent operations may lead to data inconsistency. It converts a database from one consistent state to another consistent state. It either does all or does not.

The savepoint statement allows you to create a tag point in a transaction. a transaction allows multiple tag points.

This parameter can be configured in the config. ini transaction parameter module.

[Ndbd default]

# Transaction Parameters #

MaxNoOfConcurrentTransactions: 4096

Max noofconcurrentoperations: 100000

MaxNoOfLocalOperations: 100000

BitsCN.com