-
Notifications
You must be signed in to change notification settings - Fork 257
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
"async stop" seems to conflict with the "respawn" feature #529
Comments
Can you tell me if 7e4e3cf fixes your issue? https://github.com/mozilla-services/circus/tree/fix-529 |
It sounds good @ametaireau ! We are going to do a "real life" test in a few hours to be sure. |
Cool, anyway, this will need tests as well :) |
It looks like
|
Good catch, thanks. We will add a test that covers this |
Fixed in the branch. https://github.com/mozilla-services/circus/tree/fix-529 |
added PR at #536 - LGTM. @ametaireau I will let you merge |
Okay, adding a test before that. |
should be fixed. |
During an "async stop" with a big graceful timeout, depending on the context, it seems that some processes can be respawned between the "kill -TERM" and the "kill -KILL".
I'm not completly sure about that but I have some suspicious behaviours with this kind of watcher:
and with this config file:
I'm not really sure because I am still not comfortable with the circus source but a kind of "stopping flag" seems to be missing between the kill -TERM and the kill -KILL.
This issue blocks #515 for us.
And of course, this issue is not solved by the #528 fix.
Thanks
The text was updated successfully, but these errors were encountered: