Ask Your Question

Nova-Conductor: Deadlock detected when running 'service_update': Retrying...

asked 2015-07-24 22:46:18 -0600

RHK gravatar image

updated 2015-07-25 03:10:56 -0600

In my nova-conductor log i am getting this warning, what would be the cause for this deadlock detected?

WARNING nova.db.sqlalchemy.api [req-n0234dfg5-374b-2g44-54h9-f008762567sg None] Deadlock detected when running 'service_update': Retrying...

There was some problem with rabbitmq, rabbitmq socket-descriptor reached max value.. stopped/kill the rabbitmq-server process in the controllers and started it...

After that nova-conductor logs showing above warning message.


edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2015-07-25 01:53:42 -0600

RHK gravatar image

When ever the main query was update request, if its not committed when ever second transaction i.e. update query within the trigger is executed. It has to wait for the first transaction to release the lock on the rows, which will happen after a commit on the first transaction.

As i refered in some DB forums setting the AUTONOMOUS, But what happening in the autonomous transaction?

edit flag offensive delete link more


Not sure MySQL does the same

dbaxps gravatar imagedbaxps ( 2015-07-25 07:21:33 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2015-07-24 22:46:18 -0600

Seen: 804 times

Last updated: Jul 25 '15