Recover failed staging and verify concurrent successful generation cutover - #521
Merged
Merged
Conversation
zzylol
changed the base branch from
test/collector-runtime-shared-updates
to
main
September 8, 2026 20:18
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
1 participant
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.
Before this PR
A failed Collector publication left the backend staging slot occupied, so retrying the same successor returned 409. Successful cutover under concurrent HTTP queries was not exercised.
After this PR
Failed Collector publication discards only its staged backend generation. Active generations cannot be discarded. The production-process test retries successfully while 40 requests run, verifies consistent results, rejects retired-generation writes, and consumes the successor generation through the real Collector Rust runtime.
Verification
The extended process regression failed before cleanup and passes after it. Focused lifecycle tests verify retry and active-reader protection. Stacked on #520; no automatic merge. This tests a same-semantic runtime generation successor, not arbitrary semantic workload replacement.