Red Hat Bugzilla – Bug 1258234
Deadlock in user sync causes failures in collections and aggregation after creating fk to user details.
Last modified: 2016-05-19 05:37:31 EDT
+++ This bug was initially created as a clone of Bug #1254003 +++
Description of problem:
Deadlock in user sync causes failures in collections and aggregation. The users details sync is done every minute it lock the row for update, once a hour the hourly aggregation tries to sync VM data containing users foreign key which causes deadlock due to wait on the users table update.
See Thread about this issue:
and fix in 9.3 for this:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. add many users to engine.
2. use users on some vm.
3. waiting a few hours for aggregation to start
Deadlock between aggregation (due to foreign keys) and collection.
Should not deadlock.
--- Additional comment from Yaniv Dary on 2015-08-16 09:45:01 EDT ---
--- Additional comment from Yaniv Dary on 2015-08-16 09:53:16 EDT ---
--- Additional comment from Yaniv Dary on 2015-08-16 10:42:11 EDT ---
To unblock 3.5 users that might hit this, we will remove the foreign key completely. For 3.6 we will try to find a better way to fix this, maybe by reducing the amount of updates done in each time.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
We resolved this by removing the db enforcement.