[
https://issues.apache.org/jira/browse/CASSANDRA-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-2759:
----------------------------------------
Attachment: 0001-Renew-nodeId-in-scrub-when-skipping-rows.patch
Attached patch against 0.8.
The patch also add a new startup option to renew the node id on startup. This
could be useful if someone lose one of it's sstable (because of a bad disk for
instance) and don't want to fully decommission that node.
This could arguably be splitted in another ticket though.
> Scrub could lose increments and replicate that loss
> ---------------------------------------------------
>
> Key: CASSANDRA-2759
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2759
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.0
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Labels: counters
> Fix For: 0.8.1
>
> Attachments: 0001-Renew-nodeId-in-scrub-when-skipping-rows.patch
>
>
> If scrub cannot 'repair' a corrupted row, it will skip it. On node A, if the
> row contains some sub-count for A id, those will be lost forever since A is
> the source of truth on it's current id. We should thus renew node A id when
> that happens to avoid this (not unlike we do in cleanup).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
