[
https://issues.apache.org/jira/browse/CASSANDRA-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103334#comment-13103334
]
Benjamin Coverston commented on CASSANDRA-3181:
-----------------------------------------------
Tested this a bit and I was able to reproduce the problem.
Basically what I think happened was:
# There were compactions in-flight and scheduled.
# Something happened to halt the compactions (probably restarted the server)
# https://issues.apache.org/jira/browse/CASSANDRA-2444 got in the way
I propose one of the following:
* add option in as originally proposed
OR
* put compactions on a timer and ask periodically `does any compaction need to
be done`. Also stagger the start of the compactions by some variable amount
(5-10 minutes) similar to what we did with Hinted Handoff in 0.7.
> 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: Benjamin Coverston
> Fix For: 1.0.0
>
>
> 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
