cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Schnitzerling (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-8072) Exception during startup: Unable to gossip with any seeds
Date Wed, 10 Jun 2015 11:17:01 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580409#comment-14580409
] 

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 time, 2.1.6 had seen only other nodes,
not himself. Now I deleted all data again 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
and then I try to upgrade the same node to 2.1.6 w/ write survey as well. Seems 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 works 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 like 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.bz2
>
>
> When Opscenter 4.1.4 or 5.0.1 tries to provision a 2-node DSC 2.0.10 cluster in either
ec2 or locally, an error occurs sometimes with one of the nodes 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) Exception 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.checkForEndpointCollision(StorageService.java:444)
>         at org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:655)
>         at org.apache.cassandra.service.StorageService.initServer(StorageService.java:609)
>         at org.apache.cassandra.service.StorageService.initServer(StorageService.java:502)
>         at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:378)
>         at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:496)
>         at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.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 MessagingService.java (line
701) Waiting for messaging service to quiesce
>  INFO [ACCEPT-localhost/127.0.0.1] 2014-10-06 15:54:54,327 MessagingService.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 or definition file changes in Opscenter.
> I can reproduce locally with the above steps.  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)

Mime
View raw message