Re: Heap almost full

2013-11-04 Thread Aaron Morton
) ? It's the default value of 128. Thanks, Arindam -Original Message- From: Aaron Morton [mailto:aa...@thelastpickle.com] Sent: Monday, October 28, 2013 12:09 AM To: Cassandra User Subject: Re: Heap almost full 1] [14/10/2013:19:15:08 PDT] ScheduledTasks:1: WARN GCInspector.java

RE: Heap almost full

2013-10-31 Thread Arindam Barua
Morton [mailto:aa...@thelastpickle.com] Sent: Monday, October 28, 2013 12:09 AM To: Cassandra User Subject: Re: Heap almost full 1] [14/10/2013:19:15:08 PDT] ScheduledTasks:1: WARN GCInspector.java (line 145) Heap is 0.8287082580489245 full. You may need to reduce memtable and/or cache sizes

Re: Heap almost full

2013-10-28 Thread Aaron Morton
1] [14/10/2013:19:15:08 PDT] ScheduledTasks:1: WARN GCInspector.java (line 145) Heap is 0.8287082580489245 full. You may need to reduce memtable and/or cache sizes. Cassandra will now flush up to the two largest memtables to free up memory. Adjust flush_largest_memtables_at threshold in

Re: Heap almost full

2013-10-25 Thread Alain RODRIGUEZ
If you are starting with Cassandra I really advice you to start with 1.2.11 In 1.2+ bloomfilters are off-heap, you can use vnodes... I summed up the bloom filter usage reported by nodetool cfstats in all the CFs and it was under 50 MB. This is quite a small value. Is there no error in your

Heap almost full

2013-10-15 Thread Arindam Barua
During performance testing being run on our 4 node Cassandra 1.1.5 cluster, we are seeing warning logs about the heap being almost full - [1]. I'm trying to figure out why, and how to prevent it. The tests are being run on a Cassandra ring consisting of 4 dedicated boxes with 32 GB of RAM