You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2011/06/30 20:00:30 UTC
[jira] [Commented] (CASSANDRA-2825) Auto bootstrapping the 4th node
in a 4 node cluster doesn't work, when no token explicitly assigned in
config.
[ https://issues.apache.org/jira/browse/CASSANDRA-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057960#comment-13057960 ]
Brandon Williams commented on CASSANDRA-2825:
---------------------------------------------
I'm unable to reproduce. What I don't understand is how token 61078635599166706937511052402724559481 can be involved if the first node started at 0. My ring ends up looking like:
{noformat}
Address DC Rack Status State Load Owns Token
148820376661671484777635343879628161952
10.179.65.102 datacenter1 rack1 Up Normal 315.59 MB 12.53% 0
10.179.64.227 datacenter1 rack1 Up Normal 157.76 MB 49.97% 85015475407349018891169115382886066923
10.179.111.137 datacenter1 rack1 Up Normal 78.99 MB 25.01% 127563185643974719468523634380546988377
10.179.110.154 datacenter1 rack1 Up Normal 39.55 MB 12.49% 148820376661671484777635343879628161952
{noformat}
> 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
> Assignee: Brandon Williams
> 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