You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Jonathan Ellis <jb...@gmail.com> on 2012/08/21 16:49:36 UTC
Re: Problem while configuring key and row cache?
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 <am...@gmail.com> 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
Fwd: Problem while configuring key and row cache?
Posted by Amit Handa <am...@gmail.com>.
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 <jb...@gmail.com> 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 <am...@gmail.com> 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
>
Re: Problem while configuring key and row cache?
Posted by aaron morton <aa...@thelastpickle.com>.
Use info….
$ bin/nodetool -h localhost info
…
Key Cache : size 672 (bytes), capacity 52428768 (bytes), 12 hits, 17 requests, 0.706 recent hit rate, 14400 save period in seconds
Row Cache : size 0 (bytes), capacity 0 (bytes), 0 hits, 0 requests, NaN recent hit rate, 0 save period in seconds
Cheers
-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 22/08/2012, at 5:18 PM, Amit Handa <am...@gmail.com> wrote:
> 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 <jb...@gmail.com> 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 <am...@gmail.com> 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
>>
Re: Problem while configuring key and row cache?
Posted by Amit Handa <am...@gmail.com>.
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 <jb...@gmail.com> 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 <am...@gmail.com> 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
>