Re: Too High resident memory of cassandra 2.2.8

2016-11-16 Thread ankit tyagi
> > > *From: *ankit tyagi > *Reply-To: *"user@cassandra.apache.org" > *Date: *Sunday, November 13, 2016 at 11:33 PM > *To: *"user@cassandra.apache.org" > *Subject: *Re: Too High resident memory of cassandra 2.2.8 > > > > Hi Jeff, > &

Re: Too High resident memory of cassandra 2.2.8

2016-11-14 Thread Jeff Jirsa
columnfamily/table, so if you know how many tables you have, that may be an initial lower bound guess. From: ankit tyagi Reply-To: "user@cassandra.apache.org" Date: Sunday, November 13, 2016 at 11:33 PM To: "user@cassandra.apache.org" Subject: Re: Too High resident memor

Re: Too High resident memory of cassandra 2.2.8

2016-11-13 Thread ankit tyagi
Hi Jeff, Below is the output of nodetool staus command. Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- Address Load Tokens OwnsHost ID Rack UN 192.168.68.156 *235.79 GB* 256 ? e7b1a44d-0cd2-4b60-b322-4f989933fc51 rack1 UN 192.168.68.15

Re: Too High resident memory of cassandra 2.2.8

2016-11-13 Thread Jeff Jirsa
Cassandra keeps certain data structures offheap, including bloom filters (scales with data size), compression metadata (scales with data size), and potentially memtables (scales with # of keyspaces/tables). How much data on your node? Onheap or offheap memtables? From: ankit tyagi