+1 on disabling swap
On Oct 7, 2010 3:27 PM, "Peter Schuller"
wrote:
>> The nodes are still swapping, even though the swappiness is set to zero
>> right now. After swapping comes the OOM.
>
> In addition to what's already been said, consider just flat out
> disabling swap completely, unless you ha
> The nodes are still swapping, even though the swappiness is set to zero
> right now. After swapping comes the OOM.
In addition to what's already been said, consider just flat out
disabling swap completely, unless you have other things on the machine
that cause swap to be significantly useful (i.
There is an explanation of how to lock the JVM into memory here http://www.riptano.com/blog/whats-new-cassandra-065However from the JVM Heap Size section here http://wiki.apache.org/cassandra/MemtableThresholdsFor a rough rule of thumb, Cassandra's internal datastructures will require about memtabl
On 10/6/10 9:05 AM, Utku Can Topçu wrote:
The nodes are still swapping, even though the swappiness is set to zero
right now. After swapping comes the OOM.
https://issues.apache.org/jira/browse/CASSANDRA-1214
?
=Rob
Hi Oleg,
I've been also looking into these after some research.
I've been tacking with:
1. Setting the default max and min heap from 1G to 1500M.
2. I'm not using row caches, and the key caches are set to 1000, before they
were 200K as default
3. I've lowered the memtable throughput to 32MB
4. We
>
> Hi All,We're currently starting to get OOM exceptions in our cluster. I'm
trying to push the limiations of our machines. Currently we have 1.7 G memory
(ec2-medium)I'm wondering if by tweaking some of cassandra's configuration
settings, is it possible to make it live in peace and less memory.
