Update qdrant-landing/content/documentation/guides/distributed_deployment.md

Co-authored-by: Tim Visée <tim@visee.me>
This commit is contained in:
Bastian Hofmann
2024-11-26 10:20:25 +01:00
committed by GitHub
co-authored by Tim Visée
parent ca497e87dc
commit bae99cf46e
@@ -759,7 +759,7 @@ This ensures the availability of the data in case of node failures, except if al
### Replication factor
When you create a collection, you can control how many shard replicas you'd like to store by changing the `replication_factor`. By default, `replication_factor` is set to "1", meaning no additional copy is maintained automatically. If you configured a default replication factor in the [Qdrant configuration](/documentation/guides/configuration/#configuration-options), this value will be the default for new collections instead. You can change that by setting the `replication_factor` when you create a collection.
When you create a collection, you can control how many shard replicas you'd like to store by changing the `replication_factor`. By default, `replication_factor` is set to "1", meaning no additional copy is maintained automatically. The default can be changed in the [Qdrant configuration](/documentation/guides/configuration/#configuration-options). You can change that by setting the `replication_factor` when you create a collection.
The `replication_factor` can also be updated for existing collections. In Qdrant open-source, this will not automatically create new replicas. See [Creating new Shard Replicas](#creating-new-shard-replicas) for a description on how to create them manually. But in Qdrant Cloud, including Hybrid Cloud and Private Cloud, the shards will be automatically replicated or removed if you change the `replication_factor`.