Bug #13079 NDB/cluster reports excessive wait lock timeouts on table operations

• Submitted: 9 Sep 2005 1:18
• Modified: 28 Sep 2005 12:10
• Reporter: Howard Hart
• Status: Can't repeat
• Category: MySQL Server
• Severity: S2 (Serious)
• Version: 4.1.13
• OS: Linux (Linux 2.6.12)
• CPU Architecture: Any

[9 Sep 2005 1:18] Howard Hart

Description:
When we converted our tables from InnoDB to NDB cluster, the same tables that were updating fine under InnoDB are showing a multiple table lock timeouts daily. Sample message follows:

050908  0:07:17 [ERROR] Slave: Error 'Lock wait timeout exceeded; try restarting transaction' on query. Default database: 'murphy'. Query: 'update subscriber_group set status_activation = 1 where groupid = 72092', Error_code: 1205

Current parameters in clustet config file follow:

[DB DEFAULT]
NoOfReplicas: 2
MaxNoOfConcurrentOperations: 150000
IndexMemory: 256M
DataMemory: 768M
MaxNoOfTriggers: 1000
BackupDataBufferSize: 10M
BackupLogBufferSize: 10M
BackupMemory: 20M
MaxNoOfUniqueHashIndexes: 128

How to repeat:
Unknown, other than put heavy insert load on cluster tables. Our mix could be as high as 10-20 simultaneous transactions per second.

[28 Sep 2005 12:10] Hartmut Holzgraefe

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.