Kurt Greaves commented on CASSANDRA-5836:

bq. Won't work, as shown above.
As long as there is at least 1 replica (for every range) in the source DC it 
will work. 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.

bq. I would pretty much like to avoid any special cases, if possible.
1 special seed node doesn't seem to be a big deal to me. The first seed is 
always going to be special to some degree. And in my case, it's not that 
special. You could replace it and nothing should go wrong.

If we make auto_bootstrap false by default to me that seems much more likely to 
cause the exact same configuration problem where people forget to change it to 
true for new nodes they add. It doesn't reduce complexity, just shifts it. A 
lot of people out there will already be depending on a default of true and 
changing it to false would be a pretty big surprise, even for a major version.

> 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