Public bug reported:
When user sends sigkill or sigterm signal to nova-conductor parent
process, parent process is exits immediately. Child process which is
processing the request get killed after sometime (2-3 seconds) without
completing the current request.
Meantime if new request is sent then nova-conductor does not picks that
request from rabbitmq for processing. Once nova-conductor is up and
running again then it picks the pending requests from rabbitmq for
processing.
Expected behavior:
1. conductor should complete current request before exiting - Not Good
2. conductor should not accept new request for processing - Good
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1702263
Title:
nova conductor does not exits gracefully
Status in OpenStack Compute (nova):
New
Bug description:
When user sends sigkill or sigterm signal to nova-conductor parent
process, parent process is exits immediately. Child process which is
processing the request get killed after sometime (2-3 seconds) without
completing the current request.
Meantime if new request is sent then nova-conductor does not picks
that request from rabbitmq for processing. Once nova-conductor is up
and running again then it picks the pending requests from rabbitmq for
processing.
Expected behavior:
1. conductor should complete current request before exiting - Not Good
2. conductor should not accept new request for processing - Good
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1702263/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
