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 <erick.rami...@datastax.com> wrote: > *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 considering the number of dropped messages -- > particularly the high number of dropped gossip. It's indicative of nodes > not able to communicate with each other (overloaded, unresponsive or > whatever reason) that's caused the bootstrap to fail (maybe, conjecture on > my part). Cheers! > > GOT QUESTIONS? Apache Cassandra experts from the community and DataStax > have answers! Share your expertise on https://community.datastax.com/. >
