This repository was archived by the owner on Jun 19, 2026. It is now read-only.
receive: Disable shuffle sharding for default tenant#312
Merged
Conversation
The default tenant (catch-all for requests without a tenant header) now writes to ALL endpoints instead of a sharded subset, preventing silent data loss when unattributed traffic arrives. The default tenant ID is threaded from the CLI flag through the hashring construction chain, and getTenantShardCached short-circuits to return the base ring when the tenant matches the default tenant ID. Co-authored-by: Isaac
mkusumdb
approved these changes
Mar 13, 2026
yuchen-db
added a commit
that referenced
this pull request
Mar 20, 2026
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.
2 participants
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.
The default tenant (catch-all for requests without a tenant header) now writes to ALL endpoints instead of a sharded subset. The default tenant ID is threaded from the CLI flag through the hashring construction chain, and getTenantShardCached short-circuits to return the base ring when the tenant matches the default tenant ID.
Changes
Verification