Re: Lock wait timeout exceeded; try restarting transaction
Lock wait timeout can happen if your application is experiencing a deadlock. It can also happen due to a node failure when the transaction is aborted and rolled back as a consequence of one node failing in the middle of a transaction. Finally it could be that overload causes the progress to be so slow that the timeout occurs. What happens in your case I don't know. But overload looks to be fully possible with 155 concurrent insert clients. Deadlocks should not happen if all concurrent clients are pure inserters. Node failure I presume haven't happened since you haven't mentioned it. So the most likely cause is that the system slowed down due to overload.
Subject
Views
Written By
Posted
18783
January 31, 2015 06:49AM
Re: Lock wait timeout exceeded; try restarting transaction
5791
February 18, 2015 06:28PM
3418
March 30, 2015 12:56PM
3356
March 30, 2015 12:59PM
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.