You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2016/08/11 15:34:20 UTC

[jira] [Commented] (CASSANDRA-12436) Under some races commit log may incorrectly think it has unflushed data

    [ https://issues.apache.org/jira/browse/CASSANDRA-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417444#comment-15417444 ] 

T Jake Luciani commented on CASSANDRA-12436:
--------------------------------------------

Can you explain why a empty memtable would cause a dirty section in the CL?  

Nit: [This comment|https://github.com/blambov/cassandra/commit/fc5375d3db26a7aab56f329576330c7732b8aa73#diff-98f5acb96aa6d684781936c141132e2aR1075] is no longer accurate, we don't remove the memtable anymore

> 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)