cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Anastasyev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6079) Memtables flush is delayed when having a lot of batchlog activity, making node OOM
Date Wed, 25 Sep 2013 10:10:02 GMT

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

Oleg Anastasyev commented on CASSANDRA-6079:
--------------------------------------------

ok then. started writing code ;-)
                
> Memtables flush is delayed when having a lot of batchlog activity, making node OOM
> ----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6079
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6079
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Oleg Anastasyev
>            Assignee: Oleg Anastasyev
>            Priority: Minor
>             Fix For: 1.2.11, 2.0.2
>
>         Attachments: NoWaitBatchlogCompaction.diff
>
>
> Both MeteredFlusher and BatchlogManager share the same OptionalTasks thread. So, when
batchlog manager processes its tasks no flushes can occur. Even more, batchlog manager waits
for batchlog CF compaction to finish.
> On a lot of batchlog activity this prevents memtables from flush for a long time, making
the node OOM.
> Fixed this by moving batchlog to its own thread and not waiting for batchlog compaction
to finish.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message