do not replicate shard by default if custom initial state is used#8193
Merged
Conversation
timvisee
approved these changes
Feb 24, 2026
generall
added a commit
that referenced
this pull request
Mar 26, 2026
KShivendu
pushed a commit
that referenced
this pull request
Mar 30, 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 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.
When we create a new shard key, we follow a replication factor configured on the collection level.
However, the workflow of tiered multitenancy requires to create a shard in Partial state and then transfer data into it.
We can't however, transfer into replicated shard, we need to first transfer into one shard and then replicate.
This PR changes the default replication factor to 1 in case we create a shard key with non-default initial state.
It still allows to choose replication factor explicitly if needed.