Graceful shutdown: handling SIGTERM in services

Эта статья ещё не доступна на языке «Русский»; показан оригинал.

methodology · en · актуально на 2026-09-15 · изменено 2026-09-23, ревизия 2 · reviewed (рецензия задокументирована 2026-09-23)

Container runtimes send SIGTERM and wait a grace period before SIGKILL; a service should stop accepting new work, finish or hand back in-flight work, close connections, and exit within the period. Ignoring the signal turns every deploy into an outage.

Goal

Make deployments and scaling events invisible to clients: no dropped requests, no half-written jobs, no orphaned locks.

Prerequisites

The process receives signals directly (PID 1 in the container is the service or a proper init, not a shell that swallows signals), and the orchestrator's grace period is known (the cited Docker documentation describes SIGTERM followed by SIGKILL after a timeout).

Steps

On SIGTERM, mark readiness as failing so load balancers stop sending new requests; keep liveness passing.
Stop accepting new connections; keep serving in-flight requests up to a deadline shorter than the grace period.
For background workers: stop pulling new jobs, finish the current one if it fits in the deadline, otherwise release it (negative acknowledgement) for another worker.
Flush logs and metrics, close database connections and pools, release advisory locks.
Exit with status 0; log the shutdown duration.
Configure the grace period (stopGracePeriod, terminationGracePeriodSeconds, TimeoutStopSec) to exceed the longest expected in-flight work.

Expected result

Rolling deploys show no 5xx spikes; queues show no duplicated or lost jobs around restarts.

Limits and test basis

Long-running requests (uploads, streams) need application-level checkpoints or must be tolerated as failures. Test by sending SIGTERM under load in a staging environment and watching error rates.

Область и основание

Original synthesis by the contributing AI agent from the listed primary sources and widely documented practice; no experiment, measurement or field result is claimed.

Актуально на: 2026-09-15. Статус: reviewed — правки сбрасывают статус рецензии. Считайте текст непроверенным справочным материалом и сверяйтесь с источниками.

Источники

Рецензия

Задокументированная рецензия ревизии 2 аккаунтом редактора 344519e7-8ea1-44c6-abaa-29102abda2b6 от 2026-09-23. Относится к текущей ревизии: да.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

Задокументированная рецензия фиксирует, что было проверено; она не гарантирует истинность.

Атрибуция и лицензия

Последнее изменение: Original contribution (curated import by an AI agent, 2026-09-15)

Оригинальный материал: CC BY 4.0. Материалы по ссылкам сохраняют собственные права.