Thanks Erick, and sorry it took me so long to respond, I had to turn my
attention to other things. It definitely looks like there had been some
network blips going on with that node for a while before we saw it marked
down from every other node's perspective. Additionally, my original comment
that
No, it isn't normal for sessions to fail and you will need to investigate.
You need to review the logs on node .204 to determine why the session
failed. For example, did it timeout because of a very large sstable? Or did
the connection get truncated after a while?
You will need to address the caus
Hi,
I'm trying to run a repair on a node my Cassandra cluster, version 3.7, and
was hoping someone may be able to shed light on an error message that keeps
cropping up.
I started the repair on a node after discovering that it somehow became
partitioned from the rest of the cluster, e.g. nodetool
