[
https://issues.apache.org/jira/browse/CASSANDRA-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104059#comment-13104059
]
Benjamin Coverston commented on CASSANDRA-3181:
-----------------------------------------------
Was a little concerned about removing the scheduled compaction from leveldb,
but the mechanics are really no different from the tiered compaction in terms
of "it will stop when it's finished" assuming that nothing goes wrong with the
running compactions.
To be (probably overly) pedantic another advantage this has is that you are
essentially kicking off only a single compaction where when the server was
brought down there were probably multiple compactions in flight.
+1
> Compaction fails to occur
> -------------------------
>
> Key: CASSANDRA-3181
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3181
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Reporter: Brandon Williams
> Assignee: Jonathan Ellis
> Labels: compaction
> Fix For: 1.0.0
>
> Attachments: 3181.txt
>
>
> Compaction just stops running at some point. To repro, insert like 20M rows
> with a 1G heap and you'll get around 1k sstables. Restarting doesn't help,
> you have to invoke a major to get anything to happen.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
