Cassandra Consistency Level

最新推荐文章于 2025-04-26 18:42:57 发布

lzz313

最新推荐文章于 2025-04-26 18:42:57 发布

阅读量2.9k

点赞数

分类专栏：系统架构文章标签： cassandra thread table

10 篇文章

订阅专栏

本文详细介绍了在分布式系统中进行读写操作时使用的一致性级别，包括ZERO、ANY、ONE、QUORUM及ALL等不同级别的定义及其应用场景。通过理解这些一致性级别，开发者可以更好地在性能与数据一致性之间找到平衡。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

级别	内容
`ZERO`	Ensure nothing. A write happens asynchronously in background
`ANY`	(Requires 0.6) Ensure that the write has been written to at least 1 node, including hinted recipients.
`ONE`	Ensure that the write has been written to at least 1 node's commit log and memory table before responding to the client.
`QUORUM`	Ensure that the write has been written to `<Replication> / 2 + 1` nodes before responding to the client.
`ALL`	Ensure that the write is written to all `<Replication>` nodes before responding to the client. Any unresponsive nodes will fail the operation.

级别	内容
`ZERO`	Not supported, because it doesn't make sense.
`ANY`	Not supported. You probably want ONE instead.
`ONE`	Will return the record returned by the first node to respond. A consistency check is always done in a background thread to fix any consistency issues when `ConsistencyLevel.ONE` is used. This means subsequent calls will have correct data even if the initial read gets an older value. (This is called `read repair` .)
`QUORUM`	Will query all nodes and return the record with the most recent timestamp once it has at least a majority of replicas reported. Again, the remaining replicas will be checked in the background.
`ALL`	Will query all nodes and return the record with the most recent timestamp once all nodes have replied. Any unresponsive nodes will fail the operation.