cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep Tata (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-132) Support session level consistency
Date Mon, 04 May 2009 20:28:30 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705729#action_12705729
] 

Sandeep Tata commented on CASSANDRA-132:
----------------------------------------

Point to note: today, it is possible (even on a single node) that you do an insert followed
by a get_column, and you *don't* read the latest value you inserted. The insert is sent as
a RowMutationMessage to the endpoints (even if one of them is local) and acked (in the non-blocking
variation). It is possible that this message is not received before the next get_column message
is processed.

> Support 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
>             Fix For: trunk
>
>
> 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.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message