>
> Nodes are going down due to Out of Memory and we are using 31GB heap size
> in DC1 , however in DC2 (Which serves the traffic) has 16GB heap .
> Why we had to increase heap in DC1 is because , DC1 nodes were going down
> due Out of Memory issue but DC2 nodes never went down .
>
It doesn't soun
You may find throttle rate of hinted handoff on node and adjust if needed.
nodetool gethintedhandoffthrottlekb and you may also set by nodetool
sethintedhandoffthrottlekb
I would also check disk stats where hints are stored either by sar or iostat.
Sincerely,
Aakash Pandhi
On Wednesday,
Is dc1 a simple standby DC? Or you run some operations(e.g. compute for
analysis) on the same? Have you found the root cause of the oom? Do you
see any specific Cassandra operation (e.g repair) is causing oom?
One tip: try upgrading to 3.11.6 as lots of bugs has been fixed since 3.11.0
On Wed, Fe
Nodes are going down due to Out of Memory and we are using 31GB heap size
in DC1 , however in DC2 (Which serves the traffic) has 16GB heap .
Why we had to increase heap in DC1 is because , DC1 nodes were going down
due Out of Memory issue but DC2 nodes never went down .
We also noticed below kind
