[
https://issues.apache.org/jira/browse/CASSANDRA-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731813#comment-14731813
]
Jeff Jirsa commented on CASSANDRA-5051:
---------------------------------------
I once again find myself wishing this existed, I've read through the comments
and it looks like there's nearly unanimous consensus that this is a nice thing
to have, but progress was paused waiting on 2.1 streaming. With 3.0 heading
into beta, is now a good time to nudge this? Or are there more blockers on the
horizon?
// [~cburroughs] given the choice between A, B, and C, I'd love C, because in 5
years of operating in production, I've never once had to go back and pull a
replica from a node that no longer owned it because I somehow messed up
ownership so bad I didn't have a real replica elsewhere. It's 2015, snapshots
are cheaper than ever, cleanup should be more frequent.
> Allow automatic cleanup after gc_grace
> --------------------------------------
>
> Key: CASSANDRA-5051
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5051
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Brandon Williams
> Assignee: Vijay
> Labels: vnodes
> Fix For: 3.x
>
> Attachments: 0001-5051-v4.patch, 0001-5051-v6.patch,
> 0001-5051-with-test-fixes.patch, 0001-CASSANDRA-5051.patch,
> 0002-5051-remove-upgradesstable-v4.patch,
> 0002-5051-remove-upgradesstable.patch, 0004-5051-additional-test-v4.patch,
> 5051-v2.txt
>
>
> When using vnodes, after adding a new node you have to run cleanup on all the
> machines, because you don't know which are affected and chances are it was
> most if not all of them. As an alternative to this intensive process, we
> could allow cleanup during compaction if the data is older than gc_grace (or
> perhaps some other time period since people tend to use gc_grace hacks to get
> rid of tombstones.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
