MySQL Bugs: #16867: Cluster: MySQLD Deletes should be batched to default MaxNoOfConcurrenOperations

Bug #16867	Cluster: MySQLD Deletes should be batched to default MaxNoOfConcurrenOperations
Submitted:	28 Jan 2006 16:12	Modified:	16 Mar 2006 10:35
Reporter:	Jonathan Miller	Email Updates:
Status:	Closed
Category:	Server: Docs	Severity:	S3 (Non-critical)
Version:	5.1.6-alpha	OS:	Linux (Linux 32 Bit OS)
Assigned to:	Jon Stephens	Target Version:
Triage:	D4 (Minor)

Description:
mysql> use TPCB
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> select count(*) from history;
+----------+
| count(*) |
+----------+
|   271634 |
+----------+
1 row in set (0.01 sec)

mysql> delete from history;
ERROR 1297 (HY000): Got temporary error 233 'Out of operation records in transaction
coordinator (increase MaxNoOfConcurrentOperations)' from NDBCLUSTER

I have to reduce my original configuration from

NoOfReplicas: 2
IndexMemory: 600M
DataMemory: 1400M
BackupMemory: 64M
MaxNoOfLocalOperations: 10000
MaxNoOfTables: 200
StopOnError: 1
MaxNoOfConcurrentScans: 100
DataDir: /space/run
DiskPageBufferMemory: 500M
#DiskPageBufferMemory: 4M

To this configuration before the ndbd would start with out the error listed below
NoOfReplicas: 2
IndexMemory: 500M
DataMemory: 1300M
BackupMemory: 64M
MaxNoOfLocalOperations: 10000
MaxNoOfTables: 200
StopOnError: 1
MaxNoOfConcurrentScans: 100
DataDir: /space/run
DiskPageBufferMemory: 500M
#DiskPageBufferMemory: 4M
MaxNoOfConcurrentOperations: 500000

Time: Saturday 28 January 2006 - 17:02:40
Status: Permanent error, external action needed
Message: Memory allocation failure, please decrease some configuration parameters
(Configuration error)
Error: 2327
Error data: ArrayPool<T>::setSize malloc failed
Error object: ../../../../../../storage/ndb/src/kernel/vm/ArrayPool.hpp line: 245 (block:
CMVMI)
Program: /home/ndbdev/jmiller/builds/libexec/ndbd
Pid: 26631
Trace: /space/run/ndb_2_trace.log.7
Version: Version 5.1.6 (alpha)
***EOM***

How to repeat:
See Above

Suggested fix:
Have MySQLD batch deletes to the default of  MaxNoOfConcurrentOperations:  or rase the
default value of MaxNoOfConcurrentOperations:  where MySQLD does not get the error above.

I cant see how this differs from #16869

Two different settings, 2 different bugs

Jon, could you please review the documetation on this limitation and see if we can
improve? Maybe give it a section to itself. Or added the limitation information with work
arounds to the config section talking about this setting?

My thoughts where to move, or copy or have something simular to: (from Limitations)

Note that bulk loading, TRUNCATE TABLE, and ALTER TABLE are handled as special cases by
running multiple transactions, and so are not subject to this limitation.

to http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-db-definition.html
Under "Transaction Parameters" -> MaxNoOfConcurrentTransactions

This is already documented in the Limitations section.

Not a changelog entry request, moving from Documenting status.

Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant
product(s).