cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Allen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-2825) Auto bootstrapping the 4th node in a 4 node cluster doesn't work, when no token explicitly assigned in config.
Date Fri, 24 Jun 2011 18:43:47 GMT
Auto bootstrapping the 4th node in a 4 node cluster doesn't work, when no token explicitly
assigned in config.
--------------------------------------------------------------------------------------------------------------

                 Key: CASSANDRA-2825
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2825
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 0.8.0, 0.8.1
            Reporter: Michael Allen
             Fix For: 0.8.2


This was done in sequence.  A, B, C, and D.  Node A with token 0 explicitly set in config.
 The rest with auto_bootstrap: true and no token explicitly assigned.  B and C work as expected.
D ends up stealing C's token.  

from system.log on C:

INFO [GossipStage:1] 2011-06-24 16:40:41,947 Gossiper.java (line 638) Node /10.171.47.226
is now part of the cluster
INFO [GossipStage:1] 2011-06-24 16:40:41,947 Gossiper.java (line 606) InetAddress /10.171.47.226
is now UP
INFO [GossipStage:1] 2011-06-24 16:42:09,432 StorageService.java (line 769) Nodes /10.171.47.226
and /10.171.55.77 have the same token 61078635599166706937511052402724559481.  /10.171.47.226
is the new owner
WARN [GossipStage:1] 2011-06-24 16:42:09,432 TokenMetadata.java (line 120) Token 61078635599166706937511052402724559481
changing ownership from /10.171.55.77 to /10.171.47.226




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message