MySQL Forums
Forum List  »  NDB clusters

Re: linked error "Lock wait timeout exceeded"
Posted by: Jonathan Miller
Date: June 09, 2005 07:57AM


Not sure if other users are using this cluster at the same time. You might want to review:


If the transaction is currently not performing any queries but is waiting for further user input, this parameter states the maximum time that the user can wait before the transaction is aborted.

The default for this parameter is zero (no timeout). For a real-time database that needs to ensure that no transaction keeps locks for too long a time this parameter should be set to a much smaller value. The unit is milliseconds.


When a node executes a query involving a transaction, the node waits for the other nodes in the cluster to respond before continuing. A failure to respond can occur for any of the following reasons:


The node is "dead"

The operation has entered a lock queue

The node requested to perform the action could be heavily overloaded.

This timeout parameter states how long the transaction coordinator will wait for query execution by another node before aborting the transaction, and is important for both node failure handling and deadlock detection. Setting it too high can cause a undesirable behavior in situations involving deadlocks and node failure.

The default timeout value is 1200 milliseconds (1.2 seconds).

Also, you might try smaller transaction sets.


Jonathan Miller
Austin, Texas USA
Senior QA Developer


Jumpstart your cluster!

Get training on clusters

All-in-one Enterprise-grade Database, Support and Services

Options: ReplyQuote

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.