This repository was archived by the owner on Nov 8, 2026. It is now read-only.
Repository navigation
Avoid rejecting healthy Query and Count bursts at Store admission - #128
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Queue Query/Count behind a bounded shared Store window, preserving caller contexts without adding a server-side timeout. Complete staggered initialization with up to four slots before Engine readiness, grow on healthy queued demand, and retain real-overload backoff, execution ceilings, and existing write/Worker semantics.
Local validation passes: source race/coverage and lint, 30 repeated core race-test runs, MongoDB integration, three real Elasticsearch/OpenSearch incident regressions (also confirmed failing on v0.21.0), and the complete 380-case public conformance suite. Pin batchstream/sink-production-suite#41 across PR, release, and reliability gates. Merge this server PR before the paired suite PR; no production deployment is included.