-
Notifications
You must be signed in to change notification settings - Fork 897
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
Let ansible worker gracefully stop #15643
Let ansible worker gracefully stop #15643
Conversation
https://bugzilla.redhat.com/show_bug.cgi?id=1474508 When the ansible worker is not responding, let it try to gracefuly exit by marking it as stopping. Allow, the stopping worker code to eventually kill the worker if it doesn't exit on it's own. While we're allowing the worker to gracefully exit, don't allow multiple ansible monitor workers to run at once. Normally, a replacement worker is started the moment we ask a prior worker to exit.
Checked commit jrafanie@bc8c26f with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested this out on an appliance.
The server monitor kills the thread after the stopping timeout.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Looks good
Let ansible worker gracefully stop (cherry picked from commit 3eeabd5) https://bugzilla.redhat.com/show_bug.cgi?id=1474840
Fine backport details:
|
…efully_stop Let ansible worker gracefully stop (cherry picked from commit 3eeabd5) https://bugzilla.redhat.com/show_bug.cgi?id=1474840
https://bugzilla.redhat.com/show_bug.cgi?id=1474508
When the ansible worker is not responding, let it try to gracefuly exit
by marking it as stopping. Allow, the stopping worker code to eventually
kill the worker if it doesn't exit on it's own.
While we're allowing the worker to gracefully exit, don't allow multiple
ansible monitor workers to run at once. Normally, a replacement worker
is started the moment we ask a prior worker to exit.