When running multiple parallel builds of Kiwi, sometimes we get this error
<class 'psycopg2.extensions.TransactionRollbackError'>: deadlock detected DETAIL: Process 3844877 waits for ShareLock on transaction 164249560; blocked by process 3761645. Process 3761645 waits for ShareLock on transaction 164249631; blocked by process 3844877. HINT: See server log for query details. CONTEXT: while inserting index tuple (704,4) in relation "rpminfo_unique_nvra"
I can't see whole request here, but assume that it was kiwi-build without explicit --release option. This should be possible workaround as I assume that getNextRelease returned same value for two tasks.
--release
getNextRelease
Metadata Update from @tkopecek: - Custom field Size adjusted to None
Can you check hub log for where it exactly happens?
I've played with it a bit and it is a corner-situation which was not fixed by original #788. Created #3721
Metadata Update from @tkopecek: - Issue set to the milestone: 1.33
Metadata Update from @tkopecek: - Issue set to the milestone: 1.34 (was: 1.33)
Which koji instance is this happening in? How often does it happen?
Do we have a full hub-side traceback?
The issue happened on our private Koji instance. Sadly as it was 5 months ago, I'm pretty sure it happened after that couple times but these days we are not building images that often so I don't have any recent logs with the issue… =(
Metadata Update from @tkopecek: - Issue tagged with: no_qe
Commit a8ff3d9a relates to this ticket
Commit 36764524 relates to this ticket
Metadata Update from @tkopecek: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/3637
Please continue any further discussion there.