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 configu
On Wed, Jun 18, 2014 at 4:56 AM, Jonathan Lacefield 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/doc
Hello,
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_see
Hi,
pretty sure we started out like that and had not seen any problems doing
that. On a side node, that config may become inconsistent anyway after
adding new nodes, because I think you'll need a restart of all your
nodes if you add new seeds to the yaml file. (Though that's just assumption)
My intended Cassandra cluster will have 15 nodes per DC, with 2 DCs.
I am considering using all the nodes as seed nodes.
It looks like having all the nodes as seeds should actually reduce the Gossip
overhead (See "Gossiper implementation" in
http://wiki.apache.org/cassandra/ArchitectureGossip)
Is
