欢迎投稿

今日深度:

[转]Cassandra的 Consistency Level设置,

[转]Cassandra的 Consistency Level设置,


转自:http://blog.csdn.net/lzz313/article/details/5457313
原文出处不详

写操作
级别内容
ZEROEnsure 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.
ONEEnsure that the write has been written to at least 1 node's commit log and memory table before responding to the client.
QUORUMEnsure that the write has been written to <Replication> / 2 + 1 nodes before responding to the client.
ALLEnsure that the write is written to all <Replication> nodes before responding to the client. Any unresponsive nodes will fail the operation.


读操作
级别内容
ZERONot supported, because it doesn't make sense.
ANYNot supported. You probably want ONE instead.
ONEWill 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 .)
QUORUMWill 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.
ALLWill query all nodes and return the record with the most recent timestamp once all nodes have replied. Any unresponsive nodes will fail the operation.

www.htsjk.Com true http://www.htsjk.com/cassandra/27963.html NewsArticle [转]Cassandra的 Consistency Level设置, 转自:http://blog.csdn.net/lzz313/article/details/5457313 原文出处不详 写操作 级别 内容 ZERO Ensure nothing. A write happens asynchronously in background ANY (Requires 0.6) Ensure...
相关文章
    暂无相关文章
评论暂时关闭