Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 10 Jun 2015 11:17:01 +0000 (UTC)
From: "Andreas Schnitzerling (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12746431.1412697958000.36557.1433935021936@Atlassian.JIRA>
In-Reply-To: <JIRA.12746431.1412697958000@Atlassian.JIRA>
References: <JIRA.12746431.1412697958000@Atlassian.JIRA>
 <JIRA.12746431.1412697958671@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-8072) Exception during startup:
 Unable to gossip with any seeds
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CASSANDRA-8072?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
14580409#comment-14580409 ]=20

Andreas Schnitzerling edited comment on CASSANDRA-8072 at 6/10/15 11:16 AM:
---------------------------------------------------------------------------=
-

I tried severel times to switch between 2.0.15 and 2.1.6 (start bootstr at =
2.0.15, stop, copy data to 2.1.6) but 2.1.6 doesn't start probably. One tim=
e, 2.1.6 had seen only other nodes, not himself. Now I deleted all data aga=
in on that node, removed the node with nodetool and now the bootstrap w/ 2.=
0.15 works well in write survey mode. I'll wait until bootstrap finished an=
d then I try to upgrade the same node to 2.1.6 w/ write survey as well. See=
ms like 2.1.6 is not backward compatible bootstrapping to a 2.0.x cluster.


was (Author: andie78):
I tried severel times to switch between 2.0.15 and 2.1.6 (start bootstr at =
2.0.15, stop, copy data to 2.1.6) but 2.1.6 don't start probably. One time,=
 2.1.6 have seen only other nodes, not himself. Now I deleted all again on =
that node, removed the node with nodetool and now the bootstrap w/ 2.0.15 w=
orks well in write survey mode. I'll wait until bootstrap finished and then=
 I try to upgrade the same node to 2.1.6 w/ write survey as well. Seems lik=
e 2.1.6 is not backward compatible bootstrapping to a 2.0.x cluster.

> Exception during startup: Unable to gossip with any seeds
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-8072
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8072
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Ryan Springer
>            Assignee: Brandon Williams
>             Fix For: 2.1.x, 2.0.x
>
>         Attachments: cas-dev-dt-01-uw1-cassandra-seed01_logs.tar.bz2, cas=
-dev-dt-01-uw1-cassandra-seed02_logs.tar.bz2, cas-dev-dt-01-uw1-cassandra02=
_logs.tar.bz2, casandra-system-log-with-assert-patch.log, trace_logs.tar.bz=
2
>
>
> When Opscenter 4.1.4 or 5.0.1 tries to provision a 2-node DSC 2.0.10 clus=
ter in either ec2 or locally, an error occurs sometimes with one of the nod=
es refusing to start C*.  The error in the /var/log/cassandra/system.log is=
:
> ERROR [main] 2014-10-06 15:54:52,292 CassandraDaemon.java (line 513) Exce=
ption encountered during startup
> java.lang.RuntimeException: Unable to gossip with any seeds
>         at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:=
1200)
>         at org.apache.cassandra.service.StorageService.checkForEndpointCo=
llision(StorageService.java:444)
>         at org.apache.cassandra.service.StorageService.prepareToJoin(Stor=
ageService.java:655)
>         at org.apache.cassandra.service.StorageService.initServer(Storage=
Service.java:609)
>         at org.apache.cassandra.service.StorageService.initServer(Storage=
Service.java:502)
>         at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDa=
emon.java:378)
>         at org.apache.cassandra.service.CassandraDaemon.activate(Cassandr=
aDaemon.java:496)
>         at org.apache.cassandra.service.CassandraDaemon.main(CassandraDae=
mon.java:585)
>  INFO [StorageServiceShutdownHook] 2014-10-06 15:54:52,326 Gossiper.java =
(line 1279) Announcing shutdown
>  INFO [StorageServiceShutdownHook] 2014-10-06 15:54:54,326 MessagingServi=
ce.java (line 701) Waiting for messaging service to quiesce
>  INFO [ACCEPT-localhost/127.0.0.1] 2014-10-06 15:54:54,327 MessagingServi=
ce.java (line 941) MessagingService has terminated the accept() thread
> This errors does not always occur when provisioning a 2-node cluster, but=
 probably around half of the time on only one of the nodes.  I haven't been=
 able to reproduce this error with DSC 2.0.9, and there have been no code o=
r definition file changes in Opscenter.
> I can reproduce locally with the above steps.=E2=80=82 I'm happy to test =
any proposed fixes since I'm the only person able to reproduce reliably so =
far.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)