Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

orc-agent signal handling #1

Open
Igneous opened this issue Aug 13, 2014 · 0 comments
Open

orc-agent signal handling #1

Igneous opened this issue Aug 13, 2014 · 0 comments
Milestone

Comments

@Igneous
Copy link
Owner

Igneous commented Aug 13, 2014

Currently, if orc-agent is in the middle of a handler run (like chef + chef-client), it will respond to a SIGTERM by terminating and sending SIGTERM to the processes forked from it.

We need a "graceful stop/restart" mechanism, so sending orc-agent a SIGTERM causes a check for currently running handlers. If there are currently running handlers, wait until the run finishes, then terminate.

Another thought: should we unbind from our queues and de-register our amqp consumers, so we don't recieve any more messages after a SIGTERM?

@Igneous Igneous added this to the v0.4.0 milestone Aug 13, 2014
@Igneous Igneous self-assigned this Aug 13, 2014
@Igneous Igneous modified the milestones: v0.4.0, v0.3.2 Aug 13, 2014
@Igneous Igneous removed their assignment Jun 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant