cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Axel Kämpfe (JIRA) <>
Subject [jira] [Created] (CASSANDRA-9878) Rolling Updates 2.0 to 2.1 "unable to gossip"
Date Thu, 23 Jul 2015 11:23:04 GMT
Axel Kämpfe created CASSANDRA-9878:

             Summary: Rolling Updates 2.0 to 2.1 "unable to gossip"
                 Key: CASSANDRA-9878
             Project: Cassandra
          Issue Type: Bug
            Reporter: Axel Kämpfe

Hi there,

we are currently testing an upgrade of our servers from Cassandra 2.0.16 to 2.1.8 on the EC2
service of Amazon

Usually, we launch a new server which gets the newest version and then joins the existing
ring, bootstrapping, and after some time we kill one of the old nodes.

But with the upgrade to 2.1 the new server will not join the existing ring.
INFO  [HANDSHAKE-/] 2015-07-23 11:06:14,997 - Handshaking
version with /
INFO  [HANDSHAKE-/] 2015-07-23 11:06:14,999 - Handshaking
version with /
INFO  [HANDSHAKE-/] 2015-07-23 11:06:15,000 -
Handshaking version with /
ERROR [main] 2015-07-23 11:06:46,016 - Exception encountered during
java.lang.RuntimeException: Unable to gossip with any seeds
        at org.apache.cassandra.gms.Gossiper.doShadowRound( ~[apache-cassandra-2.1.8.jar:2.1.8]
        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( [apache-cassandra-2.1.8.jar:2.1.8]
        at org.apache.cassandra.service.CassandraDaemon.activate(
        at org.apache.cassandra.service.CassandraDaemon.main( [apache-cassandra-2.1.8.jar:2.1.8]
WARN  [StorageServiceShutdownHook] 2015-07-23 11:06:46,023 - No local state
or state is in silent shutdown, not announcing shutdown
INFO  [StorageServiceShutdownHook] 2015-07-23 11:06:46,023 - Waiting
for messaging service to quiesce
INFO  [ACCEPT-/] 2015-07-23 11:06:46,045 - MessagingService
has terminated the accept() thread


our config uses the "RandomPartitioner", "SimpleSnitch" and the internal nodes ip for communication.

when i use the same config but ONLY 2.1.x Servers, everthing works perfectly, but as soon
as we start to "mix in" a new version into an "old" ring, the new servers will not "gossip"...
( so it cannot be a firewall issue, or such)

If you need any more information from my side, please let me know.

This message was sent by Atlassian JIRA

View raw message