Bug
Long running job causes simultaneous jobs to fail
Issue description
Given a long running job J1 and a shorter job J2 which started and finished during J1, there is an increased likelhood that J2 will fail with a MySQL error 1205: Lock wait timeout exceeded.
Developer comments
The topic map data is commited, but the late exception (usually during topic touch) causes the topics to have a wrong modification date & the dobjects are out of synch.
If J2, the shorter job, imports mainly new topics, the data will be commited and only when touching the topic, the lock will occur.
No longer an issue with autocommit off.
|
Work sessions2
Start |
2022-12-19T13:47:08
|
End |
2022-12-19T16:47:16
|
Participant |
Robert Cerny
|
Start |
2022-12-21T14:27:56
|
End |
2022-12-21T15:48:40
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.