[
https://issues.apache.org/jira/browse/CASSANDRA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915458#action_12915458
]
Sylvain Lebresne commented on CASSANDRA-1546:
---------------------------------------------
I'm not of what you are referring to by 'the switching of master nodes'. Each
update has a 'leader', that
takes responsibility for the update. But for the counter row itself, there is
no distinguished node.
For bootstraping nodes, as long as they aren't choose as leader (and they won't
until they are
bootstrapped), a counter row is really a run-of-the-mill row. So I don't see a
particular problem here
(unless I haven't understand what you're refering to).
> (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.0
>
> Attachments: 0001-Remove-IClock-from-internals.patch,
> 0002-Counters.patch, 0003-Generated-thrift-files-changes.patch
>
>
> 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.
