cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Springer (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-8072) Exception during startup: Unable to gossip with any seeds
Date Tue, 07 Oct 2014 16:06:34 GMT
Ryan Springer created CASSANDRA-8072:

             Summary: Exception during startup: Unable to gossip with any seeds
                 Key: CASSANDRA-8072
             Project: Cassandra
          Issue Type: Bug
            Reporter: Ryan Springer

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 (line 513) Exception encountered
during startup
java.lang.RuntimeException: Unable to gossip with any seeds
        at org.apache.cassandra.gms.Gossiper.doShadowRound(
        at org.apache.cassandra.service.StorageService.checkForEndpointCollision(
        at org.apache.cassandra.service.StorageService.prepareToJoin(
        at org.apache.cassandra.service.StorageService.initServer(
        at org.apache.cassandra.service.StorageService.initServer(
        at org.apache.cassandra.service.CassandraDaemon.setup(
        at org.apache.cassandra.service.CassandraDaemon.activate(
        at org.apache.cassandra.service.CassandraDaemon.main(
 INFO [StorageServiceShutdownHook] 2014-10-06 15:54:52,326 (line 1279) Announcing
 INFO [StorageServiceShutdownHook] 2014-10-06 15:54:54,326 (line 701)
Waiting for messaging service to quiesce
 INFO [ACCEPT-localhost/] 2014-10-06 15:54:54,327 (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.

Email: for information about how to reproduce this issue.

This message was sent by Atlassian JIRA

View raw message