cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3219) Nodes started at the same time end up with the same token
Date Fri, 16 Sep 2011 19:08:09 GMT

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

Jonathan Ellis commented on CASSANDRA-3219:
-------------------------------------------

That is what "auto" does, with the caveat that nodes need to be started 2 minutes apart so
they don't race as in Jake's example here.

> Nodes started at the same time end up with the same token
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-3219
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3219
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: T Jake Luciani
>
> Since autoboostrap is defaulted to on when you start a cluster at once (http://screenr.com/5G6)
you can end up with nodes being assigned the same token.
> {code}
> INFO 17:34:55,688 Node /67.23.43.14 is now part of the cluster
>  INFO 17:34:55,698 InetAddress /67.23.43.14 is now UP
>  INFO 17:34:55,698 Nodes /67.23.43.14 and tjake2/67.23.43.15 have the same token 8823900603000512634329811229926543166.
 Ignoring /67.23.43.14
>  INFO 17:34:55,698 Node /98.129.220.182 is now part of the cluster
>  INFO 17:34:55,698 InetAddress /98.129.220.182 is now UP
>  INFO 17:34:55,698 Nodes /98.129.220.182 and tjake2/67.23.43.15 have the same token 8823900603000512634329811229926543166.
 Ignoring /98.129.220.182
> {code}

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

        

Mime
View raw message