Extend write consistency factor text, reapply on client vs lower factor #1013
+13
−3
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.
Fixes qdrant/qdrant#4626
Rendered: https://deploy-preview-1013--condescending-goldwasser-91acf0.netlify.app/documentation/guides/distributed_deployment/#write-consistency-factor
This extends the write consistency factor description a bit. It improves on two points.
First, if a high write consistency factor is used an operation might fail to apply if there aren't enough active replicas. It now describes that the user is responsible for sending the operation again, to ensure a consistent state.
Second, this now describes that a lower write consistency factor may be used. In that case the write will be accepted if there are non-active replicas. Unresponsive replicas are marked as dead and are automatically recovered by the cluster to guarantee data consistency once available.