[
https://issues.apache.org/jira/browse/CASSANDRA-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624668#comment-13624668
]
Vijay commented on CASSANDRA-5051:
----------------------------------
Hi Jonathan, may be it will help if you add the following line in line 169
(testCleanupDuringRangeMovement)
{code}
logger.info("Node's Range: {}",
StorageService.instance.getLocalRanges(table.getName()));
{code}
the output is like this.
{code}
13/04/06 21:48:24 INFO compaction.CompactionsPurgeTest: Node's Range:
[(Token(bytes[01]),Token(bytes[02])]]
13/04/06 21:48:24 INFO compaction.CompactionsPurgeTest: Range movement
scheduled for: {(Token(bytes[02]),Token(bytes[00])]=[/127.0.0.3]}
{code}
> 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: 2.0
>
> Attachments: 0001-5051-v4.patch, 0001-5051-with-test-fixes.patch,
> 0001-CASSANDRA-5051.patch, 0002-5051-remove-upgradesstable.patch,
> 0002-5051-remove-upgradesstable-v4.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
