Add a datacenter to a single-token architecture cluster
Steps for adding a datacenter to single-token architecture clusters, not clusters using Virtual nodes.
|
Only add new nodes to the cluster. A new node is a system that HCD has never started. The node must have absolutely NO PREVIOUS DATA in the Adding nodes previously used for testing, or that have been removed from another cluster, merges the older data and its incompatible schema into the cluster and may cause data loss or corruption. |
Add a datacenter to a single-token architecture cluster
-
Ensure that you are using
NetworkTopologyStrategyfor all keyspaces. -
For each new node, edit the configuration properties in the
cassandra.yamlfile:-
Set
auto_bootstraptoFalse. -
Set the
initial_token. Be sure to offset the tokens in the new datacenter. -
Set the
cluster_name. -
Set any other non-default settings.
-
Set the seed lists. Every node in the cluster must have the same list of seeds and include at least one node from each datacenter. Typically one to three seeds are used per datacenter.
-
-
Update the relevant snitch properties file on all nodes to include the new nodes. You do not need to restart.
-
GossipingPropertyFileSnitch:cassandra-rackdc.properties -
PropertyFileSnitch:cassandra-topology.properties
-
-
Ensure that your client does not auto-detect the new nodes so that they aren’t contacted by the client until explicitly directed.
-
If using a QUORUM consistency level for reads or writes, check the
LOCAL_QUORUMorEACH_QUORUMconsistency level to make sure that the level meets the requirements for multiple datacenters. -
The
GossipingPropertyFileSnitchalways loadscassandra-topology.propertieswhen that file is present. Remove the file from each node on any new cluster or any cluster migrated from thePropertyFileSnitch. -
After all nodes are running in the cluster:
-
Change the replication factor for your keyspace for the expanded cluster.
-
Run
nodetool rebuildon each node in the new datacenter.
-
