[
https://issues.apache.org/jira/browse/CASSANDRA-13454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977571#comment-15977571
]
Blake Eggleston commented on CASSANDRA-13454:
---------------------------------------------
[~krummas], I realized I'd missed 2 cases. If the session is cancelled, or if
it's completed by the failure recovery process, a compaction won't get
submitted. I pushed up another commit, to make sure any session completion
triggers a compaction. Can you take a look?
> Start compaction when incremental repair finishes
> -------------------------------------------------
>
> Key: CASSANDRA-13454
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13454
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Blake Eggleston
> Assignee: Blake Eggleston
> Fix For: 4.0
>
>
> When an incremental repair finishes or fails, it's sstables are promoted /
> demoted on the next compaction. We should submit a compaction as soon an
> incremental repair finishes so sstables we're finished with don't spend any
> more time in their own silo than they need to.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
