Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
Date: Tue, 12 Jan 2016 15:56:20 +0100
Message-ID: 
 <CAEMjZ24nJfjUrqi156OBeNwA=v79dOUP6K_NPBnG+ES72Sgxyg@mail.gmail.com>
Subject: electricity outage problem
From: Adil <adil.chabaq@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a11c25e9aac89d1052924413a

--001a11c25e9aac89d1052924413a
Content-Type: text/plain; charset=UTF-8

Hi,

we have two DC with 5 nodes in each cluster, yesterday there was an
electricity outage causing all nodes down, we restart the clusters but when
we run nodetool status on DC1 it results that some nodes are DN, the
strange thing is that running the command from diffrent node in DC1 doesn't
give the same node in DC as own, we have noticed this message in the log
"received an invalid gossip generation for peer", does anyone know how to
resolve this problem? should we purge the gossip?

thanks

Adil

--001a11c25e9aac89d1052924413a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>we have two DC with 5 nodes in each=
 cluster, yesterday there was an electricity outage causing all nodes down,=
 we restart the clusters but when we run nodetool status on DC1 it results =
that some nodes are DN, the strange thing is that running the command from =
diffrent node in DC1 doesn&#39;t give the same node in DC as own, we have n=
oticed this message in the log &quot;received an invalid gossip generation =
for peer&quot;, does anyone know how to resolve this problem? should we pur=
ge the gossip?</div><div><br></div><div>thanks</div><div><br></div><div>Adi=
l</div></div>

--001a11c25e9aac89d1052924413a--