[
https://issues.apache.org/jira/browse/CASSANDRA-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239489#comment-13239489
]
Sylvain Lebresne commented on CASSANDRA-4079:
---------------------------------------------
The fact that the first and last token are not in the node ranges does not
imply the sstable has no data for those ranges. Also, we'd want to skip (but
not delete) the sstable if it is fully included in the new node ranges.
As a side node, I would really prefer moving this to 1.1.1 and sticking to
bug-fix-that-prevent-release for 1.1.0 at this point.
> Check SSTable range before running cleanup
> ------------------------------------------
>
> Key: CASSANDRA-4079
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4079
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Benjamin Coverston
> Assignee: Jonathan Ellis
> Priority: Minor
> Labels: compaction
> Fix For: 1.1.0
>
> Attachments: 4079.txt
>
>
> Before running a cleanup compaction on an SSTable we should check the range
> to see if the SSTable falls into the range we want to remove. If it doesn't
> we can just mark the SSTable as compacted and be done with it, if it does, we
> can no-op.
> Will not help with STCS, but for LCS, and perhaps some others we may see a
> benefit here after topology changes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
