> MAX_HEAP_SIZE="6G"
> HEAP_NEWSIZE="500M"
The new heap feels a little low, I often see 800M as a good number. It depends
on the number of cores, but if that's working stick with it.
> key_cache_size_in_mb: 512
Have you run this at the default and checked the cache hit rate using nodetool
info
It also use off-heap memory out of JVM. SerializingCacheProvider should be
one of the case.
Best Regards!
Jian Jin
2013/4/6
> Thank you Aaron and Bryan for your advice.
>
> I have changed following parameters and now Cassandra running absolutely
> fine. Please review below setting and advice
Thank you Aaron and Bryan for your advice.
I have changed following parameters and now Cassandra running
absolutely fine. Please review below setting and advice am I right or
right direction.
cassandra-env.sh
#JVM_OPTS="$JVM_OPTS -ea"
MAX_HEAP_SIZE="6G"
HEAP_NEWSIZE="500M"
cassandra.yaml
> We can see from below that you've tweaked and disabled many of the memory
> "safety valve" and other memory related settings.
Agree.
Also you are running with JVM heap size of 3.81GB which is non default. For a
16GB node I would expect 8GB.
Try restoring the yaml values to the defaults and
On Thu, Apr 4, 2013 at 1:27 AM, wrote:
>
> After some time (1 hour / 2 hour) cassandra shut services on one or two
> nodes with follwoing errors;
>
Wonder what the workload and schema is like ...
We can see from below that you've tweaked and disabled many of the memory
"safety valve" and other
Hi,
We are running 4 nodes Cassandra cluster (1.1.4) with Replica Factor 2
(DC 1) and Replica Factor 1 (DC 2) in two differnet data cnters with
network topology. Our machines are having 16GB RAM and 8 core with two
hard drives.
# /opt/apache-cassandra-1.1.4/bin/nodetool -h localhost ring
