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.

Sign up for GitHub

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

Jump to bottom

[release-4.4] Bug 1809667: Start graceful shutdown on SIGTERM #97

Merged
merged 1 commit into from
Mar 10, 2020
Merged

[release-4.4] Bug 1809667: Start graceful shutdown on SIGTERM #97

merged 1 commit into from
Mar 10, 2020

Commits on Mar 4, 2020

  1. Start graceful shutdown on SIGTERM 

    When the main process recieves SIGTERM or SIGINT, wait
ROUTER_GRACEFUL_SHUTDOWN_DELAY (default: 45) seconds and then signal
the reload script with ROUTER_SHUTDOWN=true that a graceful termination
is requested. The reload-haproxy script then invokes USR1 on the child
processes and waits ROUTER_MAX_SHUTDOWN_TIMEOUT or MAX_RELOAD_WAIT_TIME
(default 30) seconds before invoking TERM on the child processes.
If TERM is invoked the script exits with 1, indicating that not all
processes completed their work.

Clients with long running requests should set ROUTER_MAX_SHUTDOWN_TIMEOUT
as appropriate to ensure all connections exit cleanly.
    @smarterclayton
    smarterclayton authored and openshift-cherrypick-robot committed Mar 4, 2020
    Configuration menu
    Copy the full SHA
    fa0a2ad View commit details
    Browse the repository at this point in the history