Remove SELECT ... FOR UPDATE usage from ML2 type drivers
Bug #1330562 reported by
Cedric Brandily
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Cedric Brandily |
Bug Description
MySQL Galera does not support SELECT ... FOR UPDATE[1], since it has no concept of cross-node locking of records and results are non-deterministic.
We should prefer to avoid SELECT ... FOR UPDATE (sqlalchemy with_lockmode method)
[1]http://
Changed in neutron: | |
assignee: | nobody → Cedric Brandily (cbrandily) |
Changed in neutron: | |
status: | New → In Progress |
Changed in neutron: | |
milestone: | none → juno-2 |
importance: | Undecided → Medium |
Changed in neutron: | |
milestone: | juno-2 → juno-3 |
Changed in neutron: | |
milestone: | juno-3 → juno-rc1 |
Changed in neutron: | |
status: | In Progress → Fix Committed |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/100345
Review: https:/