Busy is not dead: the supervisor stops killing a working server - #495
Merged
Merged
Conversation
… server The first version allowed four misses of a ten-second /health probe. Measured 2026-09-21, it killed the server itself - at fourteen lanes and at twenty, each time about two minutes after the lanes filled: [liveness] /health did not answer (1 of 4) ... [liveness] /health did not answer (4 of 4) [liveness] the server stopped answering; ending it so the platform restarts the container [liveness] the server exited (137) With every lane working the event loop is saturated and /health takes longer than ten seconds. The server was alive and making progress, and ending it destroyed every bee's turn in flight - the protection doing more damage than what it protects against. A probe now waits LIVENESS_TIMEOUT (30 s) and twelve misses in a row are needed: about twelve minutes of silence. Both halves proven before shipping: a server answering in 3 s against a 5 s probe still running after 30 s a server frozen with SIGSTOP ended, exit 143 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
❌ Tests failed — 11/2436 failed
Failed tests
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The liveness supervisor (#494) killed the server itself at 14 and at 20 lanes, about two minutes after the lanes filled: with every lane working the event loop is saturated and
/healthtakes longer than ten seconds. The server was alive, and ending it destroyed every bee's turn in flight.Probe timeout 10 s → 30 s, misses allowed 4 → 12 (about twelve minutes of silence). Both halves proven: a server answering in 3 s against a 5 s probe is still running after 30 s; a server frozen with SIGSTOP is ended (exit 143).
🤖 Generated with Claude Code