Bringing together the Apache Cassandra experts from the community and DataStax.

Want to learn? Have a question? Want to share your expertise? You are in the right place!

Not sure where to begin? Getting Started

 

question

Gangadhara M.B avatar image
Gangadhara M.B asked Erick Ramirez answered

Which seeds should we configure on nodes in a new DC about to be added to a cluster?

[FOLLOW UP QUESTION TO #8948]

Before running rebuild on new AWS DC nodes should seed list on new DC nodes have entry of all seed node's entry of all on-prim ? or only designated single source DC seeds entries plus it's own DC seed list . Later once rebuild completes add all DC seed list to all DC nodes

seeds
10 |1000 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

1 Answer

Erick Ramirez avatar image
Erick Ramirez answered

The recommendations for the seeds list are:

  1. Specify at least two seed nodes from each DC in the cluster.
  2. Use the same seeds on all nodes in the cluster, regardless of the DC they belong to.

These recommendations apply regardless of whether you are adding new nodes.

After the new DC has been added, you can update the seeds list for the existing nodes to include seed nodes in the new DC but you don't need to restart Cassandra immediately. The restart can wait for the next scheduled restart.

Specifically in your situation, IF you are decommissioning an on-premise DC immediately after the new DC has been added, there's no reason to add the on-premise DC to the seeds list. Cheers!

Share
10 |1000 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.