Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 824A8968B for ; Fri, 3 Feb 2012 19:45:23 +0000 (UTC) Received: (qmail 8643 invoked by uid 500); 3 Feb 2012 19:45:21 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 8602 invoked by uid 500); 3 Feb 2012 19:45:20 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 8594 invoked by uid 99); 3 Feb 2012 19:45:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2012 19:45:20 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mohitanchlia@gmail.com designates 209.85.160.44 as permitted sender) Received: from [209.85.160.44] (HELO mail-pw0-f44.google.com) (209.85.160.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2012 19:45:15 +0000 Received: by pbcwz7 with SMTP id wz7so86111pbc.31 for ; Fri, 03 Feb 2012 11:44:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=vMIULJuhRpKwk64G0zi1or5ptvh3/nWx2wFjLEXKO/s=; b=ToeFz7DuIWBsJLILswlTDVKhfhNWHhzeU+fujLzff7uw+BszC94bKsFSwFVimQ2sLU yyDKQXjYmwcMwyDsdLvxG1umkI1iLk9puq/4YMULLKxFB+kPDxeH7ZRAsnR3Z4q26NGc Q5LP+5TuD0xhR+aQiZOFoDTIVUby0TqFLcUT4= MIME-Version: 1.0 Received: by 10.68.72.69 with SMTP id b5mr19798968pbv.120.1328298295294; Fri, 03 Feb 2012 11:44:55 -0800 (PST) Received: by 10.68.236.232 with HTTP; Fri, 3 Feb 2012 11:44:55 -0800 (PST) In-Reply-To: References: <1327971278879-7238582.post@n2.nabble.com> <1327971865370-7238603.post@n2.nabble.com> <4f2805c0.0849e00a.6fe0.fffff978@mx.google.com> <4F2840BF.8020405@sendmail.cz> <08C5C98A-7C47-4C26-B583-EA4E6CDE14CC@thelastpickle.com> Date: Fri, 3 Feb 2012 11:44:55 -0800 Message-ID: Subject: Re: WARN [Memtable] live ratio From: Mohit Anchlia To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Fri, Feb 3, 2012 at 8:46 AM, Jonathan Ellis wrote: > You should come up with a way to reproduce so we can fix it. :) This happens when server is idle for a while with not so much data and then you start a load like 50 write and 50 read requests per sec. We have 4 CF that we write to and then read from. > > On Fri, Feb 3, 2012 at 10:31 AM, Mohit Anchlia w= rote: >> On Fri, Feb 3, 2012 at 7:32 AM, Jonathan Ellis wrote= : >>> It's a warn because it's nonsense for the JVM to report that an column >>> + overhead, takes less space than just the column data itself. >>> >> >> But is there any action we need to take, or worry about? We trigger >> alerts based on WARN and ERROR. But if there is nothing to do then it >> probably is just an INFO. >>> On Tue, Jan 31, 2012 at 9:41 PM, Mohit Anchlia = wrote: >>>> I guess this is not really a WARN in that case. >>>> >>>> On Tue, Jan 31, 2012 at 4:29 PM, aaron morton wrote: >>>>> The ratio is the ratio of serialised bytes for a memtable to actual J= VM >>>>> allocated memory. Using a ratio below 1 would imply the JVM is using = less >>>>> bytes to store the memtable in memory than it takes to store it on di= sk >>>>> (without compression). >>>>> >>>>> The ceiling for the ratio is 64. >>>>> >>>>> The ratio is calculated periodically so if the workload changes, such= as >>>>> system start up, the number will lag behind. I would guess numbers le= ss than >>>>> 1 mean the memtable does not have any data. >>>>> >>>>> Cheers >>>>> >>>>> ----------------- >>>>> Aaron Morton >>>>> Freelance Developer >>>>> @aaronmorton >>>>> http://www.thelastpickle.com >>>>> >>>>> On 1/02/2012, at 8:27 AM, Radim Kolar wrote: >>>>> >>>>> >>>>> =A0but a ration of< =A01 may occur >>>>> >>>>> for column families with =A0a very high update to insert ratio. >>>>> >>>>> better to ask why minimum ratio is 1.0. What harm can be done with us= ing < >>>>> 1.0 ratio? >>>>> >>>>> >>> >>> >>> >>> -- >>> Jonathan Ellis >>> Project Chair, Apache Cassandra >>> co-founder of DataStax, the source for professional Cassandra support >>> http://www.datastax.com > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com