yahoo-eng-team team mailing list archive

[Rajesh Tailor <rajesh.tailor@xxxxxxxxxxx>]

Public bug reported:

When SIGHUP signal is send to nova-api service, it doesn't complete
processing of all pending requests before terminating all the processes.

Steps to reproduce:

1. Run nova-api service as a daemon.
2. Send SIGHUP signal to nova-api service.
   kill -1 <parent_process_id_of_nova_api>

After getting SIGHUP signal all the processes of nova-api stops instantly, without completing existing request, which might cause failure.
Ideally after getting the SIGHUP signal nova-api process should stop getting new requests and wait for existing requests to complete before terminating all the processes and restarting all nova-api processes.

** Affects: nova
     Importance: Undecided
     Assignee: Rajesh Tailor (rajesh-tailor)
         Status: New


** Tags: ntt

-- 
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/1334647

Title:
  Nova api service doesn't handle SIGHUP signal properly

Status in OpenStack Compute (Nova):
  New

Bug description:
  When SIGHUP signal is send to nova-api service, it doesn't complete
  processing of all pending requests before terminating all the
  processes.

  Steps to reproduce:

  1. Run nova-api service as a daemon.
  2. Send SIGHUP signal to nova-api service.
     kill -1 <parent_process_id_of_nova_api>

  After getting SIGHUP signal all the processes of nova-api stops instantly, without completing existing request, which might cause failure.
  Ideally after getting the SIGHUP signal nova-api process should stop getting new requests and wait for existing requests to complete before terminating all the processes and restarting all nova-api processes.

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