Preserve ranking cadence through Coordinator lease replacement - #405
Merged
Merged
Conversation
CountableNewt
marked this pull request as ready for review
September 13, 2026 18:43
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.
Coordinator lease replacement recreates the Wire host and previously reset ranking timing. Keep the scheduler outside the lease closure so complete cycles retain their ten-minute cadence and failed or cancelled attempts wait 60 seconds before retrying. Processing time remains part of the interval, without overlap or catch-up bursts.
Reservations remain held until awaited work exits. Success requires every language and plan to complete; a single generation timestamp is insufficient. Readiness retains the original monotonic age of that completed cycle, clears it on failure, and does not fabricate new telemetry when the host is recreated. A full process restart may still run immediately.
Validation: 11 focused scheduler/runtime/readiness tests and all 11 IndexingWorker tests passed. Production promotion follows Development PR #404 and its required CI/deployment checks. This PR follows the spill/maintenance remediation in #403. Keep memory limits, durability, backups and replicas unchanged while checking lease stability, all-language generation freshness, ingestion age and latency. The rejected worker/Redis prototype is excluded.
Refs TSW-92, TSW-114.