I resolved this by doing more rolling restarts on the nodes that had this
WARN it's just more restarts than I thought I would have to do.
annoying!
On Wed, Oct 12, 2016 at 1:08 PM, Yucheng Liu wrote:
> *Env: * apache cassandra 2.1.8, 6-nodes
>
> *Problem: *one node had ke
*Env: * apache cassandra 2.1.8, 6-nodes
*Problem: *one node had kernel panic and crashed twice this morning. seems
gossip generation was messed up. all nodes are flooded with "received an
invalid gossip generation for peer" warning messages. multiple rolling
restarts only fixed "nodetool status
