Level | Description | Usage |
---|---|---|
|
All replica nodes must acknowledge the write. |
This write consistency level provides the highest consistency, the highest latency, and the lowest availability of any level. |
|
A quorum of replica nodes across all datacenters must acknowledge the write. |
Cross-datacenter communication may incur extra latency. |
|
At least one replica node must acknowledge the write. |
Use for high availability and low consistency. Note: Astra DB does not support write consistency level |
|
At least two replica nodes must acknowledge the write. |
Similar to |
|
At least three replica nodes must acknowledge the write. |
Similar to |
|
At least one replica node must acknowledge the write, or if no replica nodes are available, a coordinator node must store a hint. If all replica nodes are down at write time, the data will not be available until the replica nodes for that partition have recovered. |
This write consistency level provides the lowest latency, the highest write availability, and the lowest consistency. Note: Astra DB does not support write consistency level |
|
A quorum of replica nodes in the local datacenter must acknowledge the write. Avoids latency of cross-datacenter communication. |
Use |
|
A quorum of replica nodes in the each datacenter must acknowledge the write. |
Use |
|
At least one replica node in the local datacenter must acknowledge the write. |
Use Note: Astra DB does not support write consistency level |
|
Write consistency level |
Use to achieve linearizable consistency for lightweight transactions. |
|
Write consistency level |
Use to achieve linearizable consistency for lightweight transactions. |
Was this helpful?
Thank you for your
feedback.