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

Update inconsistent state diagram

Browse Source
This commit is contained in:
Abdon Pijpelink
2025-10-30 12:08:54 +01:00
parent 573570747e
commit 55bd326619
2 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/guides/distributed_deployment.md
+4 -2
View File
@@ -1088,9 +1088,11 @@ Before responding to the client, the peer handling the request dispatches all op
- reads are using a partial fan-out strategy to optimize latency and availability
- writes are executed in parallel on all active sharded replicas
![Embeddings](/docs/concurrent-operations-replicas.png)
By default, concurrent updates on one point can result in an inconsistent state. For example, if two clients simultaneously update the same point in a collection with three replicas per shard. On some replicas, the point may reflect the update from one client, while on other replicas, the point may reflect the update from the other client.
However, in some cases, it is necessary to ensure additional guarantees during possible hardware instabilities, mass concurrent updates of same documents, etc.
![Two clients updating the same point at the same time.](/docs/concurrent-operations-replicas.png)
In some cases, it is necessary to ensure additional guarantees during possible hardware instabilities, mass concurrent updates of same documents, etc.
Qdrant provides a few options to control consistency guarantees: