diff options
| author | Roman Podoliaka <rpodolyaka@mirantis.com> | 2016-04-07 13:25:03 +0300 |
|---|---|---|
| committer | Roman Podoliaka <rpodolyaka@mirantis.com> | 2016-04-07 15:06:02 +0300 |
| commit | 51d46d38a1d0b5ee7023acc627d4694a0d67cce3 (patch) | |
| tree | 7d6e7a349362447cdf2849123301a9a8084c5ae8 /nova/db | |
| parent | 25ea19561b42b51b9b08aebb6f7fd1237b57631c (diff) | |
| download | nova-51d46d38a1d0b5ee7023acc627d4694a0d67cce3.tar.gz | |
db: retry instance_info_cache_update() on deadlock
If a Galera cluster is used in multi-writer mode it's possible, that
instance_info_cache_update() will be executed concurrently on two
different MySQL hosts for the very same row, which causes a deadlock
exception for one of the callers due to how Galera works internally.
This can affect operations like association or disassociation of
floating IPs, which will fail, if instance_info_cache_update() does
not handle deadlocks gracefully, i.e. is not retried.
Closes-Bug: #1567336
Change-Id: Ib5abffd94d2480dfbcc8b6cca7b1c73ce39e7d10
Diffstat (limited to 'nova/db')
| -rw-r--r-- | nova/db/sqlalchemy/api.py | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/nova/db/sqlalchemy/api.py b/nova/db/sqlalchemy/api.py index 91a4626884..6ecba17ab6 100644 --- a/nova/db/sqlalchemy/api.py +++ b/nova/db/sqlalchemy/api.py @@ -3005,6 +3005,7 @@ def instance_info_cache_get(context, instance_uuid): @require_context +@oslo_db_api.wrap_db_retry(max_retries=5, retry_on_deadlock=True) @pick_context_manager_writer def instance_info_cache_update(context, instance_uuid, values): """Update an instance info cache record in the table. |