You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it necessary to send a different signal in quit_excess_workers_for when TERM_CHILD=1 is set to ensure clean shutdown of workers under Heroku signal handling conditions? Currently it always sends QUIT
It's certainly the approach used by graceful_worker_shutdown_and_wait! and graceful_worker_shutdown!, although shutdown_everything_now! is reversed (which is confusing, but based on the default CLI options which will use graceful_worker_shutdown_and_wait when TERM_CHILD is enabled).
Is it necessary to send a different signal in
quit_excess_workers_for
whenTERM_CHILD=1
is set to ensure clean shutdown of workers under Heroku signal handling conditions? Currently it always sendsQUIT
The text was updated successfully, but these errors were encountered: