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

Supervisord behavior when receiving a SIGTERM signal #1649

Open
RazorBach opened this issue Jul 3, 2024 · 0 comments
Open

Supervisord behavior when receiving a SIGTERM signal #1649

RazorBach opened this issue Jul 3, 2024 · 0 comments

Comments

@RazorBach
Copy link

RazorBach commented Jul 3, 2024

In my supervisord config, i have several processes which includes one process A that cannot exit on SIGTERM.

After supervisord received the SIGTERM signal received SIGTERM indicating exit request
I can see some of them are killed while some processes including process A are still running.

I think it's due to the one special process A b/c after i killed -9 this process A, all remaining processes are killed immediately.

Does this mean the supervisord processes the SIGTERM signal and sends it to each processes sequentially?

Should it try to send this SIGTERM parallel to each process?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant