[
https://issues.apache.org/jira/browse/CASSANDRA-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16390903#comment-16390903
]
Oleksandr Shulgin commented on CASSANDRA-5836:
----------------------------------------------
{quote}As long as there is at least 1 replica (for every range) in the source
DC it will work.{quote}
Hm, I've tested the procedure quite a number of times and every time I forgot
to change the replication to NTS or to extend the replication to the new DC I
was getting a complaint from nodetool rebuild.
{quote}This is quite common for the case where you're adding a DC to a small
cluster. Personally I'd prefer we get rid of SimpleStrategy altogether... but
that's likely problematic/controversial.{quote}
Do you mean it is more common to see the error with a small cluster or other
way round: more common that it will work with a small cluster?
{quote}If we make auto_bootstrap false by default...{quote}
This not what I was suggesting. Maybe I didn't express myself clear enough.
What I suggest is to:
1) Allow seed nodes to bootstrap in presence of {{auto_boostrap=true}}, this
setting still being the default one.
2) Update documented procedure for setting up a new cluster to manually set
{{auto_boostrap=false}} before starting the nodes for the first time, then
remove the setting or change it to {{true}}.
This removes all special cases:
a) Setting up the first DC is then not different from setting up an additional
one w.r.t. {{auto_bootstrap}} setting.
b) Seed nodes are not different from non-seeds w.r.t. bootstrap behavior.
c) The very first seed node is not different from the rest.
> 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: [email protected]
For additional commands, e-mail: [email protected]
