unsubscribe
Hi,
I've written about this before, but I can't find the original thread.
I have one node on my 16 node cassandra cluster (running 8.1) that will
not stay running. All nodes were configured the same way, but this one
kept going down, so I changed these lines in my cassandra-env.sh:
JVM_OPT
to the
GC threshold and full GC takes around 80 seconds.
-Adi
2011/8/24 Ernst D Schoen-René:
So, we're on 8, so I don't think there's a key cache setting. Am I wrong?
here's my newest crash log:
ERROR [Thread-210] 2011-08-24 06:29:53,247 AbstractCassandraDaemon.java
(line
es to see
whats happening GC wise. Also check the GC settings as described in
cassandra-env.sh
Hope that helps.
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 24/08/2011, at 12:38 PM, Ernst D Schoen-René wrote:
Thanks,
We had already b
ee
whats happening GC wise. Also check the GC settings as described in
cassandra-env.sh
Hope that helps.
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 24/08/2011, at 12:38 PM, Ernst D Schoen-René wrote:
Thanks,
We had already been r
definitely our
experience that adding more memory per node actually makes things worse
eventually, as java starts eating up too many resources for it to handle.
On 8/23/11 5:28 PM, Adi wrote:
2011/8/23 Ernst D Schoen-René:
Hi,
I'm running a 16-node cassandra cluster, with a reasonably larg
Hi,
I'm running a 16-node cassandra cluster, with a reasonably large
amount of data per node (~1TB). Nodes have 16G ram, but heap is set to 8G.
The nodes keep stopping with this output in the log. Any ideas?
ERROR [Thread-85] 2011-08-23 21:00:38,723 AbstractCassandraDaemon.java
(line 113)
