You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@cassandra.apache.org by Mark Furlong <mf...@ancestry.com> on 2017/08/30 19:52:09 UTC

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

mfurlong@ancestry.com<ma...@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]

RE: Invalid Gossip generation

Posted by Mark Furlong <mf...@ancestry.com>.

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:flightctlr@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 <mf...@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

mfurlong@ancestry.com<ma...@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

Posted by Erick Ramirez <fl...@gmail.com>.

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 <mf...@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
>
> *mfurlong@ancestry.com <mf...@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]
>
>
>
>
>