Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 23 Sep 2013 18:19:03 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12670028.1379935215924.4216.1379960343121@arcas>
In-Reply-To: <JIRA.12670028.1379935215924@arcas>
References: <JIRA.12670028.1379935215924@arcas>
Subject: [jira] [Commented] (CASSANDRA-6079) Memtables flush is delayed when
 having a lot of batchlog activity, making node OOM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-6079:
-------------------------------------------

Remember, this is the *replay* path.  If it's running, the mutation is already delayed, probably because the target node was down.  So delaying for compactions doesn't seem like a dealbreaker to me.  Especially since that leaves more iops to keep the rest of the system healthy and not go down ourselves. :)
                
> 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