Calling all super heros.
I have a long standing Cassandra 2.1.12 ring that has an occasional node that
gets restarted and then is flagged with the invalid gossip generation error
leaving him down in nodetool status but the logs make it look like the nodes is
ok.
It’s only when I look at the
What do you recommend on taking this node out of the cluster, a decommission or
a removenode? Since the communication between nodes is getting invalid gossip
generation messages I would think a decommission might not be effective.
Thanks
Mark
801-705-7115 office
From: Erick Ramirez
ienced an invalid gossip generation
> error on one of the nodes. We have tried altering the local generation
> value without achieving the desired result. A rolling restart of this
> production cluster of 136 nodes is a last chance option. The next step we
> know is to upgrade this cluste
I have a 2.1.12 cluster and have experienced an invalid gossip generation error
on one of the nodes. We have tried altering the local generation value without
achieving the desired result. A rolling restart of this production cluster of
136 nodes is a last chance option. The next step we know
