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] > > > > >
