cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep Tata (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-132) Support (limited) session level consistency
Date Fri, 22 May 2009 01:11:45 GMT


Sandeep Tata updated CASSANDRA-132:

    Attachment: CASSANDRA-132-v3.patch

The debug comment actually says the wrong thing. You're sending to target, not to hint. This
patch fixes it too. Use instead of v2.

> Support (limited) session level consistency
> -------------------------------------------
>                 Key: CASSANDRA-132
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: trunk
>         Environment: all
>            Reporter: Sandeep Tata
>            Assignee: Sandeep Tata
>             Fix For: trunk
>         Attachments: CASSANDRA-132-v2.patch, CASSANDRA-132-v3.patch, CASSANDRA-132.patch
> 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:
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.

View raw message