Jeremiah Jordan commented on CASSANDRA-5836:

bq. I think "seed nodes can't bootstrap" is only true for the very first node 
deployed in a cluster (which must be a seed node).  Any further nodes deployed 
into a new cluster *can* bootstrap, but they *don't need* to, since there is no 

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?

> 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

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to