Skip to content
This repository has been archived by the owner on May 29, 2024. It is now read-only.

Graceful exit for SIGTERM #9

Open
afandian opened this issue Oct 19, 2016 · 2 comments
Open

Graceful exit for SIGTERM #9

afandian opened this issue Oct 19, 2016 · 2 comments
Milestone
full-production-d...

Comments

@afandian
Copy link
Contributor

The service should respond to SIGTERM by finishing off all work and stopping further inputs.
@afandian afandian changed the title Graceful exit Graceful exit for SIGTERM Oct 19, 2016
@afandian
Copy link
Contributor Author

docker stop sends SIGTERM

https://docs.docker.com/engine/reference/commandline/stop/

@afandian afandian added this to the full-production-deployment milestone Nov 29, 2016
@afandian
Copy link
Contributor Author

Should have signal handler to stop accepting new events. A 503 should be returned for new events (for the client to retry). If SIGKILL is detected before the output queue is drained, an error should be logged.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
full-production-deployment
Development

No branches or pull requests
1 participant
@afandian