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 Tue, 24 Sep 2013 17:30:02 GMT

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

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

Do you mean the replica, which is target for one of batched mutations ? I see a hint is written
by BM if it cannot deliver one of mutations serialized to backlog record (in replaySerializedMutation
and attemptDirectDelivery) , so as i understood HintManager bothers further about delivering
it to failed replica when it is back online. So as soon as BM writes a hint(s) for (all of)
failed replica(s), BM has nothing to do with batchlog record, so no all partitions scanning
neccessary.

Am I missing something again ?
                
> 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