[
https://issues.apache.org/jira/browse/CASSANDRA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922666#action_12922666
]
Kelvin Kakugawa commented on CASSANDRA-1546:
--------------------------------------------
I do like the less invasive approach to streaming that's implemented in #1546.
However, it does have a limitation.
The way ser/des is implemented, if you deserialize an LCC on a non-host
replica, it'll become a CC, forever. It works well for AES, when the data file
is deserialized post-stream.
The limitation is during RESTORE_REPLICA_COUNT or BOOTSTRAP where a node that
was previously in the replica set becomes part of the replica set, again. In
this case, when CCs are streamed back to the, now re-added, host replica, it
will discard(?) those CCs that it should treat as LCCs.
A rough solution would be to never re-add a previous node id / token to a ring,
ever. However, I don't think this is feasible. A rough example:
1) replica set: A,B,C
2) new node: D (inserted between B and C)
3) new replica set: A, B, D
4) D, is then removed from the replica set (for whatever reason).
5) when the replica set becomes A, B, and C, again, the above problem occurs.
I'm not sure this can be accounted for w/o qualifying the types of streaming
operations.
> (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.
