Amen. I believe the whole seed node/bootstrapping confusion goes against the "Why Cassandra", quoted from http://www.datastax.com/what-we-offer/products-services/datastax-enterprise/apache-cassandra
*Operational simplicity* – with all nodes in a cluster being the same, there is no complex configuration to manage so administration duties are greatly simplified. This is one area that stands out from watching the mailing list that clearly causes plenty of confusion. On Wed, Jun 18, 2014 at 2:42 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Wed, Jun 18, 2014 at 4:56 AM, Jonathan Lacefield < > jlacefi...@datastax.com> wrote: > >> What Artur is alluding to is that seed nodes do not bootstrap. >> Replacing seed nodes requires a slightly different approach for node >> replacement compared to non seed nodes. See here for more details: >> http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_replace_seed_node.html >> > > Better, OP could comment on the below JIRA ticket emphasizing the need for > fewer than 3 alternative and logically ambiguous ways to do the common > operation of replacing a seed node. > > Especially because the options say nonsensical things like : > > " > Add the replacement seed node's IP to all the node's seed lists. > You do not need to restart the nodes. > " > > If you do not restart the nodes, they do not know the replacement node is > a seed. This act seemingly cannot have meaning until the future time at > which all nodes are restarted. As detailed in the ticket, I assert that no > one understands what it actually means to be a seed, and why seeds should > or should not be able to bootstrap. > > https://issues.apache.org/jira/browse/CASSANDRA-5836 > > =Rob > >
