docs(ops): clarify fail-closed challenge and WorkLease reclaim triage - #1116
Merged
Conversation
Note unclean hung scrapes emit challenge_block, and queue timeouts after deadline should free slots via lease reclaim rather than Future.cancel.
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.
What changed
docs/README.md: fail-closedchallenge_blockvs WorkLease reclaim for capacity (timeoutqueue/boot) vs true work timeout.Why
Operators should not treat SoundCloud-class
timeout/workburns as “scale workers” when the fix is fail-closed challenge classification plus lease reclaim upstream.Risk
Review map
Review map: whole PR is small — start at
docs/README.md.Validation
make readycovered companion change.