krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-06 11:28:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs auto-sync

Browse Source
This commit is contained in:
qdrant
2023-05-26 23:50:14 +00:00
parent f3f5421226
commit 14c15d727a
11 changed files with 35 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/distributed_deployment.md
+3 -3
View File
@@ -3,7 +3,7 @@ title: Distributed deployment
weight: 100
---
Since version v0.8.0 Qdrant supports a distributed deployment mode.
As of v0.8.0 Qdrant supports a distributed deployment mode.
In this mode, multiple Qdrant services communicate with each other to distribute the data across the peers to extend the storage capabilities and increase stability.
To enable distributed deployment - enable the cluster mode in the [configuration](../configuration) or using the ENV variable: `QDRANT__CLUSTER__ENABLED=true`.
@@ -160,7 +160,7 @@ For example, if you have 3 nodes, 6 shards could be a good option.
If you want to extend your cluster with new nodes or some nodes become slower than the others, it might be helpful to re-balance the shard distribution in the cluster.
*Since version v0.9.0*, Qdrant allows moving shards between nodes in the cluster and removing nodes from the cluster.
*As of v0.9.0:* Qdrant allows moving shards between nodes in the cluster and removing nodes from the cluster.
This functionality unlocks the ability to dynamically scale the cluster size without downtime.
@@ -193,7 +193,7 @@ After that, Qdrant will exclude the node from the consensus, and the instance wi
## Replication
*Since version v0.11.0*, Qdrant allows to replicate shards between nodes in the cluster.
*As of v0.11.0:* Qdrant allows to replicate shards between nodes in the cluster.
Shard replication increases the reliability of the cluster by keeping several copies of a shard spread among the cluster.
This ensure the availability of the shards in case of node failures, except if all replicas are lost.