[
https://issues.apache.org/jira/browse/CASSANDRA-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383821#comment-16383821
]
Oleksandr Shulgin commented on CASSANDRA-5836:
----------------------------------------------
{quote}In the case where seeds nodes can not be contacted, how do you determine
if this is the first node in a cluster (so we should special case and skip
bootstrap) vs a mis-configuration or other seeds are down issues and therefor
the bootstrap should fail?{quote}
Good point. In this case I think it is worthwhile to require
{{auto_bootstrap=false}} when deploying new cluster/DCs, which also makes it
consistent (new cluster vs. new DC) and doesn't require special handling of the
very first seed. If {{auto_bootstrap=true}} it should signal the node to
expect some other nodes to be there, so bootstrap would fail in the above case,
but you won't end up with a blank node serving requests.
The implication is that after deploying a new cluster one would need to go and
update configuration to remove non-default auto_bootstrap setting, but this is
already the case when deploying a new DC, so I think it is acceptable.
> 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
