cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2825) Auto bootstrapping the 4th node in a 4 node cluster doesn't work, when no token explicitly assigned in config.
Date Tue, 19 Jul 2011 23:12:57 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068054#comment-13068054
] 

Brandon Williams commented on CASSANDRA-2825:
---------------------------------------------

Though 85070591730234615865843651857942052864 shows a load of 4.55KB when it is added, 90s
later when another node checks it will have 13.4K because it will have updated.  The reason
it has more load than the source at this point is because it flushed LocationInfo three times,
where the source only flushed it twice.  That should be rare in practice, since typically
if a cluster has no data you just start it up without bootstrapping, but still we should protect
against handing out tokens that already are in use.

> 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

        

Mime
View raw message