Masashi Ozawa created CASSANDRA-8422:
----------------------------------------

             Summary: cassandra won't start up due to "Unable to gossip with 
any seeds" on the decommissioned node
                 Key: CASSANDRA-8422
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8422
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Masashi Ozawa


- 2-node
  * nodeA - seed
  * nodeB

1. decommission nodeB from the cluster with nodetool
   when it's finished, kill cassandra process on nodeB
2. delete data from commit/cache/data directories on nodeB
3. try to start cassandra on nodeB (first time)
   => FAILED with "Unable to gossip with any seeds"
4. try to start cassandra on nodeB (second time)
  => OK

It was not a one-time shot. I tried it a several times and encountered the same 
issue for some reason.

ERROR [main] 2014-11-27 18:44:55,017 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:1211)
        at 
org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:445)
        at 
org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:659)
        at 
org.apache.cassandra.service.StorageService.initServer(StorageService.java:611)
        at 
org.apache.cassandra.service.StorageService.initServer(StorageService.java:503)
        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-11-27 18:44:55,076 Gossiper.java (line 
1307) Announcing shutdown


For the first time, it looks like that the recommission node(goo184) did not 
receive a GossipDigestAckMessage from a seed(test130) ? Don't know why.



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

Reply via email to