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_seed_node.html
Take this into consideration, coupled with the fact that nodes will require replacing along the way, when determining the right number of seeds to use per cluster. Jonathan Lacefield Solutions Architect, DataStax (404) 822 3487 <http://www.linkedin.com/in/jlacefield> <http://www.datastax.com/cassandrasummit14> On Wed, Jun 18, 2014 at 4:59 AM, Artur Kronenberg < artur.kronenb...@openmarket.com> wrote: > 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) > > > > > On 18/06/14 09:09, Peer, Oded wrote: > > 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 there any reason not do this? > > > > >
