Public bug reported:
Currently, when querying user quota usages, the query process is not
Order Preserved, this may causes deadlock in bulk creations. That is,
for example, there are 2 rows in the DB, the first call get the record
from the 1st row and lock, at the same time, an another call get the
record from the 2nd row and lock, then both calls will wait for the
other call to release the row and will cause the deadlock scenario.
Simply add order_by(id) to the query can avoid the deadlock by calls
that are not order preserved.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1485408
Title:
Deadlock when querying user quota usage.
Status in OpenStack Compute (nova):
New
Bug description:
Currently, when querying user quota usages, the query process is not
Order Preserved, this may causes deadlock in bulk creations. That is,
for example, there are 2 rows in the DB, the first call get the record
from the 1st row and lock, at the same time, an another call get the
record from the 2nd row and lock, then both calls will wait for the
other call to release the row and will cause the deadlock scenario.
Simply add order_by(id) to the query can avoid the deadlock by calls
that are not order preserved.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1485408/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
