[
https://issues.apache.org/jira/browse/CASSANDRA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927206#action_12927206
]
Kelvin Kakugawa commented on CASSANDRA-1546:
--------------------------------------------
Yes, I have the same concerns about post-stream repair. In 0.6, it was
elegant, because we easily hooked into the AES-repair SST created pre-stream.
We can deal w/ growing counters by using strategies from vector clocks--e.g.
collapse counters, if not updated after a given time period. The potential
problem w/ modifying the node ids on every range change is that it pushes the
modifications related to maintenance into the broader cluster. I'm a little
wary of this, though, because we'll have to reason about how this impacts the
whole system.
> (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.
