Repository navigation
Release 0.96.4: bound recent coordination receipt reads - #2112
Merged
Brian Krabach (bkrabach) merged 2 commits intoNov 15, 2026
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.
Busy manager conversations repeatedly scanned retained coordination receipts while constructing the latest request view. This change selects at most 32 IDs from each existing sender/target index before fetching the latest 32 exact receipts. Insertion order, self-send deduplication, transaction visibility and cancellation projection are preserved.
Release 0.96.4 is a patch for existing performance behavior. Its authored release entry needs no high-impact notice: permissions, defaults and recovery behavior are unchanged. Main owns the single normal publisher and authorized adoption, Spark-2 first, then Spark-1 and MacBook.
Validation:
Grants, proposals, watches, initial index creation and other host latency remain outside this query bound. Required CI and published-package smoke retain their normal scopes.