How to reproduce "Lock wait timeout" on production.log
The follwoing message occured on production.log, so resources of memory was tight.
ActiveRecord::StatementInvalid(Mysql2::Error: Lock wait timeout exceeded; try restarting transaction: SELECT `issues`.*FROM `issues` OORDER BY `issues`.`rgt` desc LIMIT 1 FOR UPDATE):
I think it's relevant issues with "redmine Defect #6579",
I tried to reproduce this problem with large parent-child hierarchies ticket, but can't reproduce.
I want to reproduce the problem to proposal for updating redmine3.0.0.
Could you tell me how to reproduce the conditions?
I use redmine2.6.0.
Thank you for your reply, Toshi-san!
Simultaneously updating issue tree.
Now I tried to update two tickets with same parent-child hierarchies at same time, this problem could not reproduce. (child and child, parent and grandchild)
Is my procedure correct?
RE: How to reproduce "Lock wait timeout" on production.log - Added by Toshi MARUYAMA about 3 years ago
Easy way to reproduce:
In MySQL console:
begin; select * from issues for update;
Thank you for your reply, I could reproduce.
However, it also occured the problem with non parent_child hierarchies ticket.
Is this result correct?