[
https://issues.apache.org/jira/browse/CASSANDRA-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396935#comment-16396935
]
Oleksandr Shulgin commented on CASSANDRA-5836:
----------------------------------------------
{quote}That will only occur if you've added the datacenter to replication prior
to adding the nodes in the new DC.{quote}
Ah, you're right. Looks like I've spent too much time recently trying to make
token allocation to work in 3.0...
{quote}It's perfectly acceptable to still use auto_bootstrap: false for a new
DC, even with my code changes.{quote}
I believe it would be still required to set it to false, unless you want to
replace this recommendation with running {{TRUNCATE system.available_ranges}}
post-bootstrap on every node of the new DC. Otherwise, {{nodetool rebuild}} is
not going to do anything because the new nodes would think that they already
have all the data due to bootstrap. Or am I missing something?
{quote}Otherwise how would you tell if you are the first node? Currently a seed
won't fail if you set auto_bootstrap: true and it's the first node in the
cluster, which is what you're proposing.{quote}
I would expect that it will try to contact other seeds for some time and will
fail ultimately, because they are not there. This is a pretty good indication
of being the first node IMO.
{quote}"the first node in the cluster doesn't bootstrap, all other nodes
respect the auto_bootstrap setting"{quote}
I expect that adding yet another corner case like this one is not going to make
the already complicated code easier to reason about. At the same time, new
cluster startup process can be arbitrarily complex: it doesn't matter much IMO.
You don't have data or clients and you are allowed to fail and start over
again. Much more important is predictable behavior during operations on a
cluster with the data and clients.
> Seed nodes should be able to bootstrap without manual intervention
> ------------------------------------------------------------------
>
> Key: CASSANDRA-5836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5836
> Project: Cassandra
> Issue Type: Bug
> Reporter: Bill Hathaway
> Priority: Minor
>
> The current logic doesn't allow a seed node to be bootstrapped. If a user
> wants to bootstrap a node configured as a seed (for example to replace a seed
> node via replace_token), they first need to remove the node's own IP from the
> seed list, and then start the bootstrap process. This seems like an
> unnecessary step since a node never uses itself as a seed.
> I think it would be a better experience if the logic was changed to allow a
> seed node to bootstrap without manual intervention when there are other seed
> nodes up in a ring.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
