Hi All,
I recently upgraded my non prod cluster from 3.10 to 3.11.2.
It was working fine for a 1.5 weeks then suddenly nodetool info startee
reporting 80% and more memory consumption.
Intially it was 16gb configured, then i bumped to 20gb and rebooted all 4
nodes of cluster-single DC.
Now after 8
Hello,
When you don't have any disk space anymore (or not much), there are things
you can do :
*Make some space:*
- Remove snapshots (nodetool clearsnapshot)
- Remove any heap dump that might be stored there
- Remove *old* -tmp- SSTables that could still be around.
- Truncate unused table / dat
If you have the time, I would suggest creating a prototype with both databases
and trying it out. You should also have some idea of how this system might
evolve in the future. It is important because that could very well help you
make a decision. Mongo or Cassandra may work but if your requireme
We are on cassandra 3.7 version
We have a 8 node production cluster, with 4 nodes each across 2 DC
The RF is set to 3 currently, and we have 2 large tables with upto 70Million
rows
We just upgraded our Production cluster from 4CPU , 12 GB RAM to 8 CPU 32 GB
Memory. Accordingly we increased our
Are you seeing significant issues in terms of performance? Increased
garbage collection, long pauses, or even OutOfMemory? Which garbage
collector are you using and with what settings/thresholds? Since the JVM's
garbage-collected, a bigger heap can mean a problem or it can just mean
"hasn't gott
There have been a few people who have reported it, but nobody (yet) has
offered a patch to fix it. It would be good to have a reliable way to
repro, and/or an analysis of a heap dump demonstrating the problem (what's
actually retained at the time you're OOM'ing).
On Mon, Jun 4, 2018 at 6:52 AM, Ab
Hi,
As per I understood, You increased your RAM and CPU but still, you are not
able to check free memory space.
Did you allocate Java Process Manually? As this is occurring because Java
process allocated memory automatically. for Memory visualization, please
use jconsole and check what is showing.
Jeff,
FWIW, when talking about https://issues.apache.org/jira/browse/CASSANDRA-13929,
there is a patch available since March without getting further attention.
Regards,
Thomas
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Dienstag, 05. Juni 2018 00:51
To: cassandra
Subject: Re: 3.11.2 memor
