Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Extend write consistency factor text, reapply on client vs lower factor #1013

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Extend write consistency factor text, reapply on client vs lower factor #1013

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions qdrant-landing/content/documentation/guides/distributed_deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -951,8 +951,11 @@ Qdrant provides a few options to control consistency guarantees:

### Write consistency factor

The `write_consistency_factor` represents the number of replicas that must acknowledge a write operation before responding to the client. It is set to one by default.
It can be configured at the collection's creation time.
The `write_consistency_factor` represents the number of replicas that must acknowledge a write operation before responding to the client. It is set to 1 by default.
It can be configured at the collection's creation or when updating the
collection parameters.

This value can range from 1 to the number of replicas you have for each shard.

```http
PUT /collections/{collection_name}
Expand Down Expand Up @@ -1068,7 +1071,14 @@ await client.CreateCollectionAsync(
);
```

Write operations will fail if the number of active replicas is less than the `write_consistency_factor`.
Write operations will fail if the number of active replicas is less than the
`write_consistency_factor`. In this case, the client is expected to send the
operation again to ensure a consistent state is reached.

Setting the `write_consistency_factor` to a lower value may allow accepting
writes even if there are unresponsive nodes. Unresponsive nodes are marked as
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If a write is accepted by one node, and that node restarts before it can propagate the write, will the write be lost?

dead and will automatically be recovered again once available to ensure data
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
dead and will automatically be recovered again once available to ensure data
dead and will automatically be recovered once available to ensure data

consistency.

### Read consistency

Expand Down
Loading