Invalid Gossip generation with Cassandra 2.1.12
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 other nodes logs that I see there are pointing to the invalid gossip generation error and marking him down. I know this issue has been fixed in 2.1.13 but how can I Install the fixed version and roll restart on a production ring without seeing the error? Any help would be greatly appreciated
RE: Invalid Gossip generation
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 [mailto:flightc...@gmail.com] Sent: Wednesday, August 30, 2017 7:34 PM To: user@cassandra.apache.org Subject: Re: Invalid Gossip generation Unfortunately, the only available workaround is a rolling restart of the cluster until you get the fix in C* 2.1.13 (CASSANDRA-10969<https://issues.apache.org/jira/browse/CASSANDRA-10969>). On Thu, Aug 31, 2017 at 5:52 AM, Mark Furlong <mfurl...@ancestry.com<mailto:mfurl...@ancestry.com>> wrote: 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 is to upgrade this cluster to a new version of 2.1. In the meantime is there any other way then the above mentioned to get this node communicating with the cluster? Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427<tel:(801)%20859-7427> O: 801-705-7115<tel:(801)%20705-7115> 1300 W Traverse Pkwy Lehi, UT 84043 [http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif]
Re: Invalid Gossip generation
Unfortunately, the only available workaround is a rolling restart of the cluster until you get the fix in C* 2.1.13 (CASSANDRA-10969 <https://issues.apache.org/jira/browse/CASSANDRA-10969>). On Thu, Aug 31, 2017 at 5:52 AM, Mark Furlong <mfurl...@ancestry.com> wrote: > 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 is to upgrade this cluster to a new version of 2.1. In the meantime is > there any other way then the above mentioned to get this node communicating > with the cluster? > > > > *Mark Furlong* > > Sr. Database Administrator > > *mfurl...@ancestry.com <mfurl...@ancestry.com>* > M: 801-859-7427 <(801)%20859-7427> > > O: 801-705-7115 <(801)%20705-7115> > > 1300 W Traverse Pkwy > > Lehi, UT 84043 > > > > > > [image: http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif] > > > > >
Invalid Gossip generation
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 is to upgrade this cluster to a new version of 2.1. In the meantime is there any other way then the above mentioned to get this node communicating with the cluster? Mark Furlong Sr. Database Administrator mfurl...@ancestry.com<mailto:mfurl...@ancestry.com> M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043 [http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif]
