[
https://issues.apache.org/jira/browse/CASSANDRA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Tata updated CASSANDRA-132:
-----------------------------------
Description:
Limited session-level consistency: if the client connects to a node and
performs operations on rows/keys that are local to that node (in that node's
key range), we should be able to guarantee read-your-writes consistency. If the
session ends because of a failure, and the client has to reconnect, there are
no guarantees across the sessions.
(This is a common practical variation of eventual consistency, see:
http://www.allthingsdistributed.com/2008/12/eventually_consistent.html for
context.)
Supporting this for a "local" sessions is significantly easier than supporting
session level consistency when the node does not own the data. A non-owning
node that is reading values from a remote replica will need to either do
a) quorum reads and writes to guarantee session level read-your-writes
b) pick at least one node to block on and stick to that node as a "master" for
the session.
was:
Limited session-level consistency: if the client connects to a node and
performs operations on rows that are local to that node, we should be able to
guarantee read-your-writes consistency. If the session ends because of a
failure, and the client has to reconnect, you only provide eventual consistency
across the sessions.
(This is a common practical variation of evantual consistency, see:
http://www.allthingsdistributed.com/2008/12/eventually_consistent.html for
context.)
Summary: Support (limited) session level consistency (was: Support
session level consistency)
> Support (limited) session level consistency
> -------------------------------------------
>
> Key: CASSANDRA-132
> URL: https://issues.apache.org/jira/browse/CASSANDRA-132
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: trunk
> Environment: all
> Reporter: Sandeep Tata
> Assignee: Sandeep Tata
> Fix For: trunk
>
>
> Limited session-level consistency: if the client connects to a node and
> performs operations on rows/keys that are local to that node (in that node's
> key range), we should be able to guarantee read-your-writes consistency. If
> the session ends because of a failure, and the client has to reconnect, there
> are no guarantees across the sessions.
> (This is a common practical variation of eventual consistency, see:
> http://www.allthingsdistributed.com/2008/12/eventually_consistent.html for
> context.)
> Supporting this for a "local" sessions is significantly easier than
> supporting session level consistency when the node does not own the data. A
> non-owning node that is reading values from a remote replica will need to
> either do
> a) quorum reads and writes to guarantee session level read-your-writes
> b) pick at least one node to block on and stick to that node as a "master"
> for the session.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
