yahoo-eng-team team mailing list archive

[Abhishek Kekane <abhishek.kekane@xxxxxxxxxxx>]

Public bug reported:

When user sends sigkill signal to nova-scheduler parent process, parent
process terminates immediately without processing the current request.
Old message remains in rabbitmq. If new request is sent then it remains
in rabbitmq.

When nova-scheduler is up again then it picks all requests from rabbitmq
for processing.

Note:
If user sends sigterm signal to nova-scheduler then parent process waits until current request is completed.

Expected behavior:
1. scheduler should complete current request before exiting - Not Good
2. scheduler should not accept new request for processing - Good

** Affects: nova
     Importance: Undecided
     Assignee: Abhishek Kekane (abhishek-kekane)
         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/1702268

Title:
  scheduler service does not exit gracefully on receiving sigkill signal

Status in OpenStack Compute (nova):
  New

Bug description:
  When user sends sigkill signal to nova-scheduler parent process,
  parent process terminates immediately without processing the current
  request. Old message remains in rabbitmq. If new request is sent then
  it remains in rabbitmq.

  When nova-scheduler is up again then it picks all requests from
  rabbitmq for processing.

  Note:
  If user sends sigterm signal to nova-scheduler then parent process waits until current request is completed.

  Expected behavior:
  1. scheduler should complete current request before exiting - Not Good
  2. scheduler should not accept new request for processing - Good

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1702268/+subscriptions