[
https://issues.apache.org/jira/browse/CASSANDRA-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804863#comment-13804863
]
Jonathan Ellis commented on CASSANDRA-6216:
-------------------------------------------
bq. should we not pick those sstables which have the largest overlapping with
sstables in the higer level.
+1. IIRC HyperDex does this in their leveldb fork.
bq. this might cause starvation to some sstables as they wont get a chance to
compact.
Well, if they're worse candidates, I'm okay with starving them. :)
(We will force compaction of an sstable that has too many expired tombstones
already, so tombstones living forever shouldn't be a problem.)
> Level Compaction should persist last compacted key per level
> ------------------------------------------------------------
>
> Key: CASSANDRA-6216
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6216
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: sankalp kohli
> Assignee: sankalp kohli
> Priority: Minor
>
> Level compaction does not persist the last compacted key per level. This is
> important for higher levels.
> The sstables with higher token and in higher levels wont get a chance to
> compact as the last compacted key will get reset after a restart.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
