ML2 delete_port operation currently involves locking ports
and bindings tables which may lead to DBDeadlock errors in certain
cases when several ports are deleted concurrently.
That may happen due to specifics of Galera working in active-active
mode: it may throw deadlock errors when it fails to validate
a change with other members of the cluster.
The fix adds retries to delete port operation to overcome such
deadlocks
Reviewed: https:/ /review. openstack. org/180466 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=45ea2cf1003 3e12c63b8ce2cd7 8b04755d0aba64
Committed: https:/
Submitter: Jenkins
Branch: master
commit 45ea2cf10033e12 c63b8ce2cd78b04 755d0aba64
Author: Oleg Bondarev <email address hidden>
Date: Wed May 6 12:50:11 2015 +0300
Wrap ML2 delete_port with db retry decorator
ML2 delete_port operation currently involves locking ports
and bindings tables which may lead to DBDeadlock errors in certain
cases when several ports are deleted concurrently.
That may happen due to specifics of Galera working in active-active
mode: it may throw deadlock errors when it fails to validate
a change with other members of the cluster.
The fix adds retries to delete port operation to overcome such
deadlocks
Closes-Bug: #1422504 70d74314c3c9185 7dc709b2d9b
Change-Id: I684691d59c5ac3