Re: Nodetool info for heap usage

2018-10-23 Thread Horia Mocioi
curate to monitor memory usage, intially with 3.1.0 we had monitoring nodetool infor for heap usage and it never reported this information as high,after upgrading to 3.11.2 we started getting high usage using nodetool info later upgraded to 3.11.3 and same behaviour. Just wanted make sure if monutorin

Re: Nodetool info for heap usage

2018-10-22 Thread Anup Shirolkar
at 07:16, Abdul Patel wrote: > Hi All, > > Is nodetool info information is accurate to monitor memory usage, intially > with 3.1.0 we had monitoring nodetool infor for heap usage and it never > reported this information as high,after upgrading to 3.11.2 we started > gettin

Nodetool info for heap usage

2018-10-22 Thread Abdul Patel
Hi All, Is nodetool info information is accurate to monitor memory usage, intially with 3.1.0 we had monitoring nodetool infor for heap usage and it never reported this information as high,after upgrading to 3.11.2 we started getting high usage using nodetool info later upgraded to 3.11.3

Re: select fields and heap usage

2018-03-20 Thread Ali Hubail
complaints and to improve our customer service, email communications may be monitored and telephone calls may be recorded. Jean Carlo <jean.jeancar...@gmail.com> 03/20/2018 05:42 AM Please respond to user@cassandra.apache.org To user@cassandra.apache.org, cc Subject select fields an

select fields and heap usage

2018-03-20 Thread Jean Carlo
Hello, Talking about heap pressure, is there any difference between make a '*select **' and a '*select field *'? Is cassandra taking into the heap the whole partition to make the merge doesn't matters if we make a select of few rows ? Best greatings Jean Carlo "The best way to predict the

heap usage

2013-02-15 Thread Reik Schatz
Hi, recently we are hitting some OOM: Java heap space, so I was investigating how the heap is used in Cassandra 1.2+ We use the calculated 4G heap. Our cluster is 6 nodes, around 750 GB data and a replication factor of 3. Row cache is disabled. All key cache and memtable settings are left at

Re: heap usage

2013-02-15 Thread Blake Manders
You probably want to look at your bloom filters. Be forewarned though, they're difficult to change; changes to bloom filter settings only apply to new SSTables, so they might not be noticeable until a few compactions have taken place. If that is your issue, and your usage model fits it, a good

Re: heap usage

2013-02-15 Thread Edward Capriolo
It is not going to be true for long that LCS does not require bloom filters. https://issues.apache.org/jira/browse/CASSANDRA-5029 Apparently, without bloom filters there are issues. On Fri, Feb 15, 2013 at 7:29 AM, Blake Manders bl...@crosspixel.net wrote: You probably want to look at your

Re: heap usage

2013-02-15 Thread Wei Zhu
@cassandra.apache.org Sent: Friday, February 15, 2013 8:16:23 AM Subject: Re: heap usage It is not going to be true for long that LCS does not require bloom filters. https://issues.apache.org/jira/browse/CASSANDRA-5029 Apparently, without bloom filters there are issues. On Fri, Feb 15, 2013 at 7:29 AM, Blake

Re: heap usage

2013-02-15 Thread Bryan Talbot
Aren't bloom filters kept off heap in 1.2? https://issues.apache.org/jira/browse/CASSANDRA-4865 Disabling bloom filters also disables tombstone removal as well, so don't disable them if you delete anything. https://issues.apache.org/jira/browse/CASSANDRA-5182 I believe that the index samples