[
https://issues.apache.org/jira/browse/CASSANDRA-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103952#comment-13103952
]
Jonathan Ellis commented on CASSANDRA-3181:
-------------------------------------------
bq. CASSANDRA-2444 got in the way
I'm not sure what the right solution is here. I buy the premise of 2444 that
you don't necessarily want to get hammered by compaction when you're first
starting up (warming up caches). So I don't think "check for compactions ever
N seconds" is a great policy. But, I'm not sure "check every N seconds,
starting M minutes after startup" is great either because it's not something a
user will just guess when he's wondering "why aren't compactions happening yet?"
Any other ideas?
> 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
