Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <8698900.14971287690521561.JavaMail.jira@thor>
Date: Thu, 21 Oct 2010 15:48:41 -0400 (EDT)
From: "Stu Hood (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1546) (Yet another) approach to
 counting
In-Reply-To: <14882558.418751285581874401.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Stu Hood commented on CASSANDRA-1546:
-------------------------------------

If you end up with LCC/CCs for 4 different participating nodes when your replication factor is only 3, it seems like there is bound to be a deterministic approach to incorporating the 4th LCC. My understanding is slim, but at read time, if one of the member LCCs has completely disappeared from gossip (and responsibility), then you can deterministically choose one of the remaining nodes to incorporate the counts, right?

> (Yet another) approach to counting
> ----------------------------------
>
>                 Key: CASSANDRA-1546
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1546
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 0.7.1
>
>         Attachments: 0001-v2-Remove-IClock-from-internals.patch, 0001-v3-Remove-IClock-from-internals.txt, 0001-v4-Counters.patch, 0002-v2-Counters.patch, 0002-v3-Counters.txt, 0002-v4-thrift-changes.patch, 0003-v2-Thrift-changes.patch, 0003-v3-Thrift-changes.txt, marker_idea.txt
>
>
> This could be described as a mix between CASSANDRA-1072 without clocks and CASSANDRA-1421.
> More details in the comment below.

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