[
https://issues.apache.org/jira/browse/CASSANDRA-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388935#comment-16388935
]
Kurt Greaves commented on CASSANDRA-5836:
-----------------------------------------
bq. But the above only holds in the context of the default auto_bootstrap=true
setting. If we require that it is set to false when deploying new clusters/DCs,
the problem goes away and we don't need a special case for the very first node.
I don't think this is necessary. My patch above should only make the very first
node in a cluster a special case, all new seeds regardless of DC would not have
the bootstrap problem. We wouldn't want to be overriding the behaviour of
{{autobootstrap}} for these cases anyway.
bq. The only case I see when SimpleStrategy can actually work with multiple DCs
is when you start multi-DC from scratch. The auth keyspace you will want to
change to use NTS and replicate to all DCs, but you might not care about the
other two non-local system keyspaces.
SimpleStrategy does not care about DC's, it only cares about token order in the
ring. Whether or not it makes sense for adding DC's, we currently create 3
keyspaces using SimpleStrategy. I don't think it's acceptable to say you have
to change these to NTS prior to adding a new DC. It's perfectly acceptable to
use SimpleStrategy for {{system_traces}} and {{system_distributed}}.
{{system_auth}} also works but it's a bad idea.
bq. But are you referring here to a case where you would add a new DC to a
cluster with data already in the original DC and still using SimpleStrategy,
Kurt Greaves? To me that doesn't seem to be practical.
bq. Any reason why would you want to go this way instead of the proper nodetool
rebuild?
Yes. Not that the data in those keyspaces is terribly important to me, but it
might be to some people. Using nodetool rebuild when you've used SimpleStrategy
will end up with data loss/won't work.
bq. how do you make new seeds bootstrap?
If only the first seed is special this is not a problem. Other seeds can
bootstrap if they so desire (auto_bootstrap: true).
> 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
