We are running MySQL ndbcluster (Server version: 5.6.15-ndb-7.3.4-cluster).
While running update queries, we were repeatedly receiving the following error:
Got temporary error 233 'Out of operation records in transaction coordinator (increase MaxNoOfConcurrentOperations)' from NDBCLUSTER
As per MySQL documentation the config.ini was modified:
[NDBD DEFAULT]
MaxNoOfConcurrentOperations=1000000
MaxNoOfConcurrentTransactions=163840
After that we restarted the management, NDBD and API node(s). At this stage we are still receiving the error, and our question is:
How can the current(running) value of the parameters(MaxNoOfConcurrentOperations and MaxNoOfConcurrentTransactions) be read to ensure the changes made in both the node(s) did kick in.
Please suggest.
Thanks
While running update queries, we were repeatedly receiving the following error:
Got temporary error 233 'Out of operation records in transaction coordinator (increase MaxNoOfConcurrentOperations)' from NDBCLUSTER
As per MySQL documentation the config.ini was modified:
[NDBD DEFAULT]
MaxNoOfConcurrentOperations=1000000
MaxNoOfConcurrentTransactions=163840
After that we restarted the management, NDBD and API node(s). At this stage we are still receiving the error, and our question is:
How can the current(running) value of the parameters(MaxNoOfConcurrentOperations and MaxNoOfConcurrentTransactions) be read to ensure the changes made in both the node(s) did kick in.
Please suggest.
Thanks