[
https://issues.apache.org/jira/browse/CASSANDRA-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103949#comment-13103949
]
Sylvain Lebresne commented on CASSANDRA-3181:
---------------------------------------------
bq. . So I think repair was blocking minors
repair should be on its own executor now, so it shouldn't block minors.
bq. a compaction failed unexpectedly
hum, a compaction failing shouldn't stop other compactions. Otherwise this is
worth fixing.
bq. I'm pretty sure that we're just looking at a problem where a server
restarts and there is no more activity triggering a flush
If that's the case, then is there really much we want to do ? And even if we
want, we should move that to 1.0.1. Just want to make sure this doesn't hide a
real, unknown, problem.
> 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
