[
https://issues.apache.org/jira/browse/CASSANDRA-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419005#comment-15419005
]
T Jake Luciani commented on CASSANDRA-12436:
--------------------------------------------
Committed to 3.0 as {{5cef78af9214308ef817de43ec36054a2549329c}}
Committed to 3.9 as {{ca556c442049808c013bd20649d6611eb4a01a61}}
Does this also affect 3.8? If so we should cherry pick to there. [~blambov] can
you post a 3.8 branch if so?
> Under some races commit log may incorrectly think it has unflushed data
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-12436
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12436
> Project: Cassandra
> Issue Type: Bug
> Reporter: Branimir Lambov
> Assignee: Branimir Lambov
> Fix For: 3.0.9, 3.9
>
>
> This can mainfest itself as a "Failed to force-recycle all segments; at least
> one segment is still in use with dirty CFs." message after CASSANDRA-11828.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
