[
https://issues.apache.org/jira/browse/CASSANDRA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107890#comment-13107890
]
Jonathan Ellis commented on CASSANDRA-3219:
-------------------------------------------
bq. when Jake encountered that problem he was trying to set up an initial
cluster before having set up schemas and inserted some data
Maybe, but it sounded to me like the situation was "I was adding new nodes to
an existing cluster, and they picked the same token." Which as I pointed out
in chat is NOT a new problem, but it's one we should address.
Another way of looking at my patch is, it's okay for defaults to give you
something suboptimal (random tokens) but it's not okay for it to give you
something broken (two nodes w/ same token). If you want auto token picking and
its potential downsides, you need to opt in. (And hopefully read the comments
and go with manual token assignment instead.)
bq. I find it weird to consider that a non-starter so rapidly
Because demo-ability matters.
> 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
> Assignee: Jonathan Ellis
> Labels: bootstrap
> Fix For: 1.0.0
>
> Attachments: 3219.txt, 3219_v2.patch
>
>
> 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
