Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A9B7910EE5 for ; Wed, 25 Sep 2013 10:11:08 +0000 (UTC) Received: (qmail 49971 invoked by uid 500); 25 Sep 2013 10:10:39 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 49749 invoked by uid 500); 25 Sep 2013 10:10:24 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 49623 invoked by uid 99); 25 Sep 2013 10:10:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 10:10:02 +0000 Date: Wed, 25 Sep 2013 10:10:02 +0000 (UTC) From: "Oleg Anastasyev (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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