Compute node stats update may lead to DBDeadlock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Gary Kotton | ||
Havana |
Fix Released
|
High
|
Rohit Karajgi |
Bug Description
During a tempest run, when a compute node's usage stats are updated on the DB as part of resource claiming for an instance spawn, we hit a DBDeadlock exception:
File ".../nova/
with rt.instance_
File ".../nova/
return f(*args, **kwargs)
File ".../nova/
self._
File ".../nova/
context, self.compute_node, values, prune_stats)
File ".../nova/
prune_stats)
File ".../nova/
prune_
File ".../nova/
return self._invoke(
File ".../nova/
return cast_or_call(ctxt, msg, **self.kwargs)
File ".../nova/
result = rpc.call(context, real_topic, msg, timeout)
File ".../nova/
return _get_impl(
File ".../nova/
rpc_amqp.
File ".../nova/
rv = list(rv)
File ".../nova/
raise result
RemoteError: Remote error: DBDeadlock (OperationalError) (1213, 'Deadlock found when trying to get lock; try restarting transaction') 'UPDATE compute_nodes SET updated_at=%s, hypervisor_
(A more complete log is at http://
Can someone characterize the conditions under which this type of errors can occur?
Perhaps sqlchemy.
description: | updated |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Gary Kotton (garyk) |
Changed in nova: | |
milestone: | none → icehouse-1 |
tags: | added: db grizzly-backport-potential havana-backport-potential |
Changed in nova: | |
milestone: | icehouse-1 → icehouse-2 |
Changed in nova: | |
milestone: | icehouse-2 → icehouse-3 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
tags: | removed: grizzly-backport-potential havana-backport-potential in-stable-havana |
Changed in nova: | |
milestone: | icehouse-3 → 2014.1 |
Another issue reported that is similar to this is:
https:/ /bugs.launchpad .net/nova/ +bug/1250836