fix: drain builder before mutating worker runtime - #195
Merged
Merged
Conversation
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.
Summary
Root cause
Production Live E2E run #45 was interrupted by worker deployment: pm2 began deleting bloom-builder-worker roughly 100ms before the active runtime bridge exited with code null. Stage 1 (#193) added worker-side drain/busy markers and is already deployed.
Verification
Rollout
After merge, verify Deploy to Server and Deploy Bloom Worker both succeed and confirm the worker deploy logs show Builder drain request/completion, runtime bridge smoke, and both worker processes online.