Skip to content

do not replicate shard by default if custom initial state is used#8193

Merged
generall merged 1 commit into
devfrom
partial-shard-key-replicas
Feb 24, 2026
Merged

do not replicate shard by default if custom initial state is used#8193
generall merged 1 commit into
devfrom
partial-shard-key-replicas

Conversation

@generall
Copy link
Copy Markdown
Member

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.

@generall generall requested a review from timvisee February 20, 2026 19:06
coderabbitai[bot]

This comment was marked as resolved.

@generall generall merged commit f07897f into dev Feb 24, 2026
15 checks passed
@generall generall deleted the partial-shard-key-replicas branch February 24, 2026 10:49
@qdrant qdrant deleted a comment from coderabbitai Bot Feb 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants