Hi all,
Why glance is not using Launcher/ProcessLauncher (oslo-incubator) for its wsgi
service like it is used in other openstack projects i.e. nova, cinder, keystone
etc.
As of now when SIGHUP signal is sent to glance-api parent process, it calls the
callback handler and then throws OSError.
The OSError is thrown because os.wait system call was interrupted due to SIGHUP
callback handler.
As a result of this parent process closes the server socket.
All the child processes also gets terminated without completing existing api
requests because the server socket is already closed and the service doesn't
restart.
Ideally when SIGHUP signal is received by the glance-api process, it should
process all the pending requests and then restart the glance-api service.
If (oslo-incubator) Launcher/ProcessLauncher is used in glance then it will
handle service restart on 'SIGHUP' signal properly.
Can anyone please let me know what will be the positive/negative impact of
using Launcher/ProcessLauncher (oslo-incubator) in glance?
Thank You,
Rajesh Tailor
______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain legally privileged, confidential,
and proprietary data. If you are not the intended recipient, please advise the
sender by replying promptly to this email and then delete and destroy this
email and any attachments without any further use, copying or forwarding
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
