On Thu, Feb 22, 2018 at 11:06 PM, Oleksandr Shulgin <
> On Thu, Feb 22, 2018 at 5:42 PM, Jonathan Haddad <j...@jonhaddad.com>
>> If it's a new cluster, there's no need to disable auto_bootstrap.
>> That setting prevents the first node in the second DC from being a
>> replica for all the data in the first DC.
> Not sure where did you get that from? Whether a node in a new DC would
> become a replica for any data or not is controlled by RFs of the relevant
> keyspaces, and not by the auto_bootstrap setting.
> Seeds don't bootstrap by the way, changing the setting on those nodes
>> doesn't do anything.
> Yes, seeds don't bootstrap. But why? I don't think I ever seen a
> comprehensive explanation of this.
The meaning of seed in the most common sense is "connect to this host, and
use it as the starting point for adding this node to the cluster".
If you specify that a joining node is the seed, the implication is that
it's already a member of the cluster (or, alternatively, authoritative on
the cluster's state). Given that implication, why would it make sense to
then proceed to bootstrap? By setting it as a seed, you've told it that it
already knows what the cluster is.