[ https://issues.apache.org/jira/browse/CASSANDRA-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751853#comment-15751853 ]
Jon Haddad commented on CASSANDRA-5051: --------------------------------------- Maybe time for this in 4.0? > Allow automatic cleanup after gc_grace > -------------------------------------- > > Key: CASSANDRA-5051 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5051 > Project: Cassandra > Issue Type: New Feature > 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)