[ https://issues.apache.org/jira/browse/CASSANDRA-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710134#comment-13710134 ]
Tyler Hobbs commented on CASSANDRA-5722: ---------------------------------------- Sorry for needing to be brief. That commit just got me thinking about findPosition()'s behavior, since I borrowed parts of it for firstKeyBeyond(). Not a necessary change for this ticket, just a potential optimization we may have missed in getPosition() and some explanation for my own understanding of the performance characteristics. > Cleanup should skip sstables that don't contain data outside a nodes ranges > --------------------------------------------------------------------------- > > Key: CASSANDRA-5722 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5722 > Project: Cassandra > Issue Type: Improvement > Reporter: Nick Bailey > Assignee: Tyler Hobbs > Fix For: 2.0.1 > > Attachments: 0001-Skip-cleanup-when-unneeded.patch > > > Right now cleanup is optimized to simply delete sstables that *only* contain > data that doesn't belong on the node, for all other sstables though, it will > read them, check each row, and write out new sstables. > Cleanup could be optimized to look at an sstable and determine that all data > within the sstable does belong on a node, and therefore skip re-writing that > sstable. This would make cleanup essentially a noop in the case where all > data on a node belongs on that node. -- 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