Red Hat Bugzilla – Bug 1274074
LockAcquisitionException when binding to pools
Last modified: 2016-06-15 09:54:36 EDT
e underlying situation is now on the Corporate Escalation List. I set the customer escalation flag on this BZ.
We will need more attention on this BZ. Please increase its priority.
Hi Filip - Could you please add me to the Service Desk Incident. Perhaps we can raise it's priority in the queue to help unblock you.
We have solved the deadlock issue; however, it then results in an issue with lock-waits timing out. In MySQL, the default lock wait timeout is 50s. Depending on the amount of data and the load on some of our services, binds can take anywhere from 5s to 30s. The portal is enqueuing all of the bind jobs at the same time so they are more or less getting run simultaneous. If a user asks for 6 binds and each bind takes 10s, then obviously one job is going to time out.
There are a few solutions:
1. Decrease bind time dramatically.
2. Only enqueue 2 or 3 jobs per consumer at a time.
3. Do not perform async binds at all.
I am currently exploring option 1 as I think it results in the best user experience. Option 2 is definitely workable as well. Option 3 will suffice as a workaround.
We're working on getting option 3 in place while writing code for a longer term fix.
This was fixed in master with
In 0.9.51 this was fixed with
Moving to closed as the patches have been merged & built