[
https://issues.apache.org/jira/browse/CASSANDRA-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003458#comment-13003458
]
T Jake Luciani commented on CASSANDRA-1938:
-------------------------------------------
Ryan we left it in incase the compaction was running on a "latest" version
sstable.
Is there anyway to deal with this by tracking the CounterColumns in
-Statistics.db?
I would imagine most people would not be using counters so seems like a waste
to throw away echoRow for the non-counter case.
> Use UUID as node identifiers in counters instead of IP addresses
> -----------------------------------------------------------------
>
> Key: CASSANDRA-1938
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1938
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 0.8
>
> Attachments: 0001-Use-uuid-instead-of-IP-for-counters.patch,
> 0002-Merge-old-shard-locally.patch, 0003-Thrift-change-to-CfDef.patch,
> 1938_discussion
>
> Original Estimate: 56h
> Remaining Estimate: 56h
>
> The use of IP addresses as node identifiers in the partition of a given
> counter is fragile. Changes of the node's IP addresses can result in data
> loss. This patch proposes to use UUIDs instead.
> NOTE: this breaks the on-disk file format (for counters)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
