forked from mtusi2026/mtusi2026lab2
On SIGTERM gunicorn closed the listener at once, so a request already queued on the closing socket reached the balancer as a dropped connection after sending: a retry for GET and keyed messages, a 502 for user, chat and login posts. Now each worker first raises a draining flag and keeps serving for DRAIN_SECONDS (2 s by default, above the 1.5 s worst detection of a 503): readiness answers 503 unavailable, liveness stays 200, and the balancer takes the replica out while it is still healthy. Only then uvicorn closes the listener and finishes accepted requests within SHUTDOWN_TIMEOUT_SECONDS minus the window, so gunicorn graceful_timeout stays 5 s. The worker runs a uvicorn Server subclass whose main loop adds the window after the exit signal; UvicornWorker._serve is overridden to use it. Tests check readiness under the flag and run real gunicorn on a free port: during the window ready is 503 and live 200, the port closes after the window, a registration accepted before SIGTERM and finished after the port closed still gets 201, and the master exits with code 0 before the shutdown limit. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>