Database deadlocks in neutron-server logs
Bug #1401879 reported by
Eugene Nikanorov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Invalid
|
High
|
Alexander Ignatov | ||
6.0.x |
Invalid
|
High
|
Alexander Ignatov | ||
6.1.x |
Invalid
|
High
|
Alexander Ignatov |
Bug Description
Several thousands of 'deadlock' errors like:
Exception during message handling: (OperationalError) (1213, 'Deadlock found when trying to get lock; try restarting transaction')
Could be found in neutron-server logs during rally tests run.
There is a suspicion that it is a result of the fix that has changed transaction isolation level for mysql.
There are also similar bugs that result in deadlock/lock wait timeouts but happen quite rarely.
Info: This errors appears when we try run transaction in agent tables
description: | updated |
tags: | added: neutron |
Changed in mos: | |
importance: | Undecided → Critical |
assignee: | nobody → Eugene Nikanorov (enikanorov) |
status: | New → Confirmed |
tags: | added: scale |
description: | updated |
tags: | added: release-notes |
description: | updated |
tags: | added: staging |
tags: | removed: scale |
tags: | removed: release-notes |
Changed in mos: | |
status: | Confirmed → Invalid |
To post a comment you must log in.
Please don't mark it as dublicate of https:/ /bugs.launchpad .net/mos/ +bug/1392386 It is different issues.