This is not causing any issues and with the restart it goes away. But I
would like understand why this is happening only on certain DC but not all
DC.
I am depending on this output to find whether a node is doing any streams
or not.
On Fri, Apr 17, 2020 at 2:37 AM Erick Ramirez
wrote:
> The node
The node which shows that bootstrap session from January 31 won't go away
until you restart it. But you don't need to restart unless it's affecting
the node's operation. Cheers!
>
Hello Erick,
I can see the bootstrap message "Bootstrap
24359390-4443-11ea-af19-1fbf341b76a0" every time, I spin up a 3rd
datacenter. I can confirm that there are no network issues and cluster is
not overloaded, as this is the new cluster without any data. 1 and 2
regions don't have any Bootstrap
>
> I could re-produce this behavior all the times in 3rd datacenter and there
> is network connectivity issues. Also cluster is not overloaded as this is
> brand new cluster.
I don't quite understand what you mean. What can you re-produce? It would
be good if you could elaborate. Cheers!
I could re-produce this behavior all the times in 3rd datacenter and there
is network connectivity issues. Also cluster is not overloaded as this is
brand new cluster.
On Wednesday, April 15, 2020, Erick Ramirez
wrote:
> *Bootstrap 24359390-4443-11ea-af19-1fbf341b76a0*
>>
>>
> That bootstrap ses
>
> *Bootstrap 24359390-4443-11ea-af19-1fbf341b76a0*
>
>
That bootstrap session ID is from January 31 8:02am Pacific time. I'm
going to speculate that you attempted to bootstrap a node and encountered
issues. The stream likely got orphaned as it seems you have some issues
with your cluster consider
Hello,
I have 3 region Cassandra clusters and I am trying to look at the "nodetool
netstats" output, I see two different outputs in 1,2 regions vs region 3.
There is a Bootstrap message in Region 3 and where are it's not present in
Region 1 and Region 2, though all the nodes were bootstrapped.
*R
