128GB RAM -> that's a good news, you have plenty of room to increase Cassandra
heap size. You can start with, let's say, 12GB in jvm.options or 24GB if you
use G1 GC. Let us know if the node starts and if DEBUG/TRACE is useful.
You can also try "strace -f -p ..." command to see if the process i
Hi Roman
yes I modified the .yaml after the issue.
The problem is this, if I restart a node in DC-FIRENZE than
it not startup I tried first one node and then the second one
with the same results.
these are the server resources
memory 128G
Ok so all nodes in Firenze are down. I thought only one was KO.
After a first look at cassandra.yaml the only issue I saw is seeds: the line
you commented out was correct (one seed per DC). But I guess you modified it
after the issue.
You should fix the swap issue.
Also can you add more heap
Hi Romain,
you are right, is not possible to work in these towns
furtunally I live in Pisa :-).
I sow the errors and corrected them, except the swap one.
The process stuks, I let it run for 1 day without results.
This is the output of nodetool status from the
Hi Francesco, it can't work! Milano and Firenze, oh boy, Calcio vs Calcio
Storico X-D
Ok more seriously, "Updating topology ..." is not a problem. But you have low
resources and system misconfiguration:
- Small heap size: 3.867GiB From the logs: "Unable to lock JVM memory
(ENOMEM). This can r
Hi to all,
I have a problem with distribuited cluster configuration.
This is a test environment
Cassandra version is 3.11.3
2 site Milan and Florence
2 servers on each site
1 common "cluster-name" and 2 DC
First installation and startup
