You should not bootstrap with mixed cluster. First you should upgrade and
then bootstrap a new node. If you are not able to upgrade due to disk space
constraints while running upgradesstable, then
1. Reduce the number of threads for upgradesstable (--jobs parameter). By
default it is 2. You can do
Hi,
We are facing some issue in bootstrapping new node in 3.11.0 and
bootstrapping is failing.
We have two tasks here :
1. Expand the cluster (Due to disk concern and dropped mutation)
2. Upgrade the cluster from 3.11.0 to 3.11.5 because of various bugs we are
hitting in 3.11.0 .
So my question h
I tried to change the heap size from 31GB to 62GB on the bootstrapping node
because , I noticed that , when it reached the mid way of bootstrapping ,
heap reached to around 90% or more and node just freeze .
But still it is the same behavior , it again reached midway and heap again
reached 90% or m
