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 3D7FED750 for ; Wed, 22 Aug 2012 05:28:12 +0000 (UTC) Received: (qmail 63221 invoked by uid 500); 22 Aug 2012 05:28:09 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 62911 invoked by uid 500); 22 Aug 2012 05:28:08 -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 62869 invoked by uid 99); 22 Aug 2012 05:28:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2012 05:28:06 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of amithanda01@gmail.com designates 209.85.220.172 as permitted sender) Received: from [209.85.220.172] (HELO mail-vc0-f172.google.com) (209.85.220.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2012 05:27:59 +0000 Received: by vcbfo14 with SMTP id fo14so674825vcb.31 for ; Tue, 21 Aug 2012 22:27:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HmOEY66FND2Fm7L02RXelv5IaIhmmU4iKDB6II3+wFc=; b=AUp4YkiOVz5L1Mo5jOp2rQxqpDPEzdNGeePQYjVNuqu3C40ZjRIFIQLMCXjiojarf6 v6Z0WUPNOBhKi5Xq8pcUgq6kXzGACNT2fbhT/UKG4Z9whZn0cpM0YzBjDr/tWDLcM3DD M1zjYi2vRUlNhl9AnReSzMF/VQebpr+lMVHp33Ch+7wLt3vWMDFtaFRaWKC6ecXNOnxw 5TOBGldOqcpdhkHVEjMSQ6QX0i4wKuTUDpmIqPsi7UqItaGJ/ucm6t2OmepHeAJl2Bq4 OBlMIYx95P3FOhZpM2XYzbaec0/JUL1epnXidwdOlYNO14UJRHKu7Y9KLDuMC6muqf7J SlAA== MIME-Version: 1.0 Received: by 10.52.26.137 with SMTP id l9mr13057915vdg.62.1345613258245; Tue, 21 Aug 2012 22:27:38 -0700 (PDT) Received: by 10.58.68.106 with HTTP; Tue, 21 Aug 2012 22:27:38 -0700 (PDT) In-Reply-To: References: Date: Wed, 22 Aug 2012 10:57:38 +0530 Message-ID: Subject: Fwd: Problem while configuring key and row cache? From: Amit Handa To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=20cf307cfd364344d004c7d4005e --20cf307cfd364344d004c7d4005e Content-Type: text/plain; charset=ISO-8859-1 Hi, Thanks Jonathan for your reply. I modified key_cache_size_in_mb and row_cache_size_in_mb values inside cassandra.yaml. but not able to see it's effect using command " *./nodetool -h 107.108.189.212 cfstats*". Can u let me know how to verify that the setting for key_cache_size and row_chache_size has taken place. With Regards, Amit On Tue, Aug 21, 2012 at 8:19 PM, Jonathan Ellis wrote: > setcachecapacity is obsolete in 1.1+. Looks like we missed removing > it from nodetool. See > http://www.datastax.com/dev/blog/caching-in-cassandra-1-1 for > background. > > (Moving to users@.) > > On Tue, Aug 21, 2012 at 8:19 AM, Amit Handa wrote: > > I started exploring apache cassandra 1.1.3. I am facing problem with how > to > > improve performance of cassandra using caching configurations. > > I tried setting following configurations: > > > > ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 200005 0 > > ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 0 200005 > > ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 200005 > 200005 > > ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 444 444 > > > > > > But when i am checking that this particula configuration are really been > > configured using command: > > ./nodetool -h 107.108.189.212 cfstats > > > > it's showing following results for keySpace DemoUser and column Family > > Users: > > *Keyspace: DemoUser > > Read Count: 21914 > > Read Latency: 0.08268495026010769 ms. > > Write Count: 87656 > > Write Latency: 0.06009481381765082 ms. > > Pending Tasks: 0 > > Column Family: Users > > SSTable count: 1 > > Space used (live): 1573335 > > Space used (total): 1573335 > > Number of Keys (estimate): 22016 > > Memtable Columns Count: 0 > > Memtable Data Size: 0 > > Memtable Switch Count: 1 > > Read Count: 21914 > > Read Latency: 0.083 ms. > > Write Count: 87656 > > Write Latency: 0.060 ms. > > Pending Tasks: 0 > > Bloom Filter False Postives: 0 > > Bloom Filter False Ratio: 0.00000 > > Bloom Filter Space Used: 41104 > > Compacted row minimum size: 150 > > Compacted row maximum size: 179 > > Compacted row mean size: 179 * > > > > I am unable to see the effect of above setcachecapacity command. Let me > > know how i can configure the cache capacity, and check it's effect. > > > > With Regards, > > Amit > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com > --20cf307cfd364344d004c7d4005e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

Thanks Jonathan for your = reply.
I modified key_cache_size_in_mb and row_cache_size_in_mb v= alues inside cassandra.yaml. but not able to see it's effect using comm= and "=A0./nodetool -h 107.108.189.212 cfstats". Can u let = me know how to verify that the setting for key_cache_size and row_chache_si= ze has taken place.

With Regards,
Amit

=

On Tue, Aug 21, 2012 at 8:19 PM, Jonatha= n Ellis <jbellis@gmail.com> wrote:
setcachecapacity is obsolete in 1.1+. =A0Loo= ks like we missed removing
it from nodetool. =A0See
http://www.datastax.com/dev/blog/caching-in-cassandra-1-1 = for
background.

(Moving to users@.)

On Tue, Aug 21, 2012 at 8:19 AM, Amit Handa <amithanda01@gmail.com> wrote:
> I started exploring apache cassandra 1.1.3. I am facing problem with h= ow to
> improve performance of cassandra using caching configurations.
> I tried setting following configurations:
>
> ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 200005 0=
> ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 0 200005=
> ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 200005 2= 00005
> ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 444 444<= br> >
>
> But when i am checking that this particula configuration are really be= en
> configured using command:
> ./nodetool -h 107.108.189.212 cfstats
>
> it's showing following results for keySpace DemoUser and column Fa= mily
> Users:
> *Keyspace: DemoUser
> =A0 =A0 Read Count: 21914
> =A0 =A0 Read Latency: 0.08268495026010769 ms.
> =A0 =A0 Write Count: 87656
> =A0 =A0 Write Latency: 0.06009481381765082 ms.
> =A0 =A0 Pending Tasks: 0
> =A0 =A0 =A0 =A0 Column Family: Users
> =A0 =A0 =A0 =A0 SSTable count: 1
> =A0 =A0 =A0 =A0 Space used (live): 1573335
> =A0 =A0 =A0 =A0 Space used (total): 1573335
> =A0 =A0 =A0 =A0 Number of Keys (estimate): 22016
> =A0 =A0 =A0 =A0 Memtable Columns Count: 0
> =A0 =A0 =A0 =A0 Memtable Data Size: 0
> =A0 =A0 =A0 =A0 Memtable Switch Count: 1
> =A0 =A0 =A0 =A0 Read Count: 21914
> =A0 =A0 =A0 =A0 Read Latency: 0.083 ms.
> =A0 =A0 =A0 =A0 Write Count: 87656
> =A0 =A0 =A0 =A0 Write Latency: 0.060 ms.
> =A0 =A0 =A0 =A0 Pending Tasks: 0
> =A0 =A0 =A0 =A0 Bloom Filter False Postives: 0
> =A0 =A0 =A0 =A0 Bloom Filter False Ratio: 0.00000
> =A0 =A0 =A0 =A0 Bloom Filter Space Used: 41104
> =A0 =A0 =A0 =A0 Compacted row minimum size: 150
> =A0 =A0 =A0 =A0 Compacted row maximum size: 179
> =A0 =A0 =A0 =A0 Compacted row mean size: 179 *
>
> I am unable to see the effect of above setcachecapacity command. Let m= e
> know how i can configure the cache capacity, and check it's effect= .
>
> With Regards,
> Amit



--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.c= om


--20cf307cfd364344d004c7d4005e--