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 1AA92119F7 for ; Tue, 22 Apr 2014 21:56:21 +0000 (UTC) Received: (qmail 99344 invoked by uid 500); 22 Apr 2014 21:56:17 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 99299 invoked by uid 500); 22 Apr 2014 21:56:16 -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 99284 invoked by uid 99); 22 Apr 2014 21:56:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Apr 2014 21:56:16 +0000 Date: Tue, 22 Apr 2014 21:56:16 +0000 (UTC) From: "Aleksey Yeschenko (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-6944) liveRatio jumps to max when Memtable is empty 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-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977512#comment-13977512 ] Aleksey Yeschenko commented on CASSANDRA-6944: ---------------------------------------------- I say it's not a problem after CASSANDRA-6945 (in fact, this scenario was one of the reasons for 6945 in the first place). The new memtable would inherit both the live ratio and calculatedAt. So as soon as some data starts flowing into the memtable, the ratio will be recalculated. 64 will never stuck for long. > liveRatio jumps to max when Memtable is empty > --------------------------------------------- > > Key: CASSANDRA-6944 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6944 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: SUSE Linux Enterprise 11 (64-bit) > Reporter: Erik Hansen > Assignee: Aleksey Yeschenko > Priority: Minor > Labels: memtables > > liveRatio calculation on an empty memtable results in a value of Infinity since memtable.currentSize=0. Infinity then gets capped at the liveRatio max of 64. > {noformat} > WARN [MemoryMeter:1] 2014-03-19 09:26:59,483 Memtable.java (line 441) setting live ratio to maximum of 64.0 instead of Infinity > INFO [MemoryMeter:1] 2014-03-19 09:26:59,485 Memtable.java (line 452) CFS(Keyspace='system', ColumnFamily='compactions_in_progress') liveRatio is 64.0 (just-counted was 64.0). calculation took 7ms for 0 cells > {noformat} > Jumping liveRatio to the max value based on an empty Memtable leads to more frequent flushing than may be necessary. > CASSANDRA-4243 previously addressed this issue, but was resolved as fixed by CASSANDRA-3741. It does not appear this issue has been fixed as of 2.0.5 -- This message was sent by Atlassian JIRA (v6.2#6252)