Create a Scylla Cluster - Multi Data Centers (DC)¶
Consult with the table below if each node in the cluster has internal IP for internal DC communication and external IP for cross DC communication.
Single Multi Data Centers Configuration Table¶
|seeds||External IP address|
|listen_address||Internal IP address|
|rpc_address||Internal IP address|
|broadcast_address||External IP address|
|broadcast_rpc_address||External IP address|
If the node have two physical network interfaces in a multi-datacenter installation.
listen_address to this node’s private IP or hostname.
broadcast_address to the second IP or hostname (for communication between datacenters).
listen_on_broadcast_address to true.
Open the storage_port or ssl_storage_port on the public IP firewall.
- Make sure that all the ports are open.
- Obtain the IP addresses of all nodes which have been created for the cluster.
- Select a unique name as
cluster_namefor the cluster (identical for all the nodes in the cluster).
- Decide which nodes will be the seed nodes (It is recommended to define more than one node as a seed node).
- Choose which snitch to use (identical for all the nodes in the cluster). For a production system, it is recommended to use a DC-aware snitch, which can support a
NetworkTopologyStrategyreplication-strategy for your Keyspaces.
- Decide the name of the rack, for example: RACK1, RACK2 or RC1, RC2.
- Decide the name of the data-center, for example: DC1, DC2 or US-DC, ASIA-DC.
Choose the data-center name carefully, it is not possible to rename a data-center later
When working with production environments you must choose one of the snitches below:
These steps need to be done for each of the nodes in the new cluster.
1. Install Scylla on a node, see Getting Started for further instructions, create as many nodes that you need Follow the Scylla install procedure up to scylla.yaml configuration phase.
In case that your node starts during the process follow these instructions
2. In the
scylla.yaml file edit the parameters listed below,
the file can be found under
- cluster_name - Set the selected cluster_name
- seeds - Set the selected seed nodes
- listen_address - IP address that the Scylla use to connect to other Scylla nodes in the cluster
- auto_bootstrap - By default, this parameter is set to true, it allow new nodes to migrate data to themselves automatically
- endpoint_snitch - Set the selected snitch
- rpc_address - Address for client connection (Thrift, CQLSH)
3. In the
cassandra-rackdc.properties file, edit the rack and data-center information.
The file can be found under
To save bandwidth, add the
prefer_local=true parameter. Scylla will use the node private (local) IP address when the nodes are in the same data-center.
- After you have installed and configured Scylla and edit
scylla.yamlon all nodes, start the seeds nodes one at a time, and then start the rest of the nodes in your cluster
5. Verify that the node added to the cluster
In this example we will show how to install a nine nodes cluster, we will have six seed nodes
- Installing nine Scylla nodes, three nodes in each data-center (U.S, ASIA, EUROPE) and two seed nodes in each data-center, the IP’s are:
U.S Data-center Node# Private IP Public IP Node1 192.168.1.201 18.104.22.168 (seed) Node2 192.168.1.202 22.214.171.124 (seed) Node3 192.168.1.203 126.96.36.199 ASIA Data-center Node# Private IP Public IP Node4 192.168.1.204 188.8.131.52 (seed) Node5 192.168.1.205 184.108.40.206 (seed) Node6 192.168.1.206 220.127.116.11 EUROPE Data-center Node# Private IP Public IP Node7 192.168.1.207 18.104.22.168 (seed) Node8 192.168.1.208 22.214.171.124 (seed) Node9 192.168.1.209 126.96.36.199
- In each Scylla node, edit the
scylla.yamlfile (example of one node per DC below)
U.S Data-center - 192.168.1.201
cluster_name: 'multi_dc_demo' seeds: "188.8.131.52,184.108.40.206,220.127.116.11,18.104.22.168,22.214.171.124,126.96.36.199" endpoint_snitch: GossipingPropertyFileSnitch rpc_address: "192.168.1.201" listen_address: "192.168.1.201" broadcast_address: "188.8.131.52" broadcast_rpc_address: "184.108.40.206" listen_on_broadcast_address: true (optional)
ASIA Data-center - 192.168.1.204
cluster_name: 'multi_dc_demo' seeds: "220.127.116.11,18.104.22.168,22.214.171.124,126.96.36.199,188.8.131.52,184.108.40.206" endpoint_snitch: GossipingPropertyFileSnitch rpc_address: "192.168.1.204" listen_address: "192.168.1.204" broadcast_address: "220.127.116.11" broadcast_rpc_address: "18.104.22.168" listen_on_broadcast_address: true (optional)
EUROPE Data-center - 192.168.1.207
cluster_name: 'multi_dc_demo' seeds: "22.214.171.124,126.96.36.199,188.8.131.52,184.108.40.206,220.127.116.11,18.104.22.168" endpoint_snitch: GossipingPropertyFileSnitch rpc_address: "192.168.1.207" listen_address: "192.168.1.207" broadcast_address: "22.214.171.124" broadcast_rpc_address: "126.96.36.199" listen_on_broadcast_address: true (optional)
- In each Scylla node, edit the
cassandra-rackdc.propertiesfile with the relevant rack and data-center information
- Starting Scylla nodes, starting with the seed nodes.
192.168.1.201 192.168.1.202 192.168.1.204 192.168.1.205 192.168.1.207 192.168.1.208
And than we will start the remaining of the nodes
192.168.1.203 192.168.1.206 192.168.1.209
- Verify that the node added to the cluster by using the
nodetool status Datacenter: US-DC ========================= Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- Address Load Tokens Owns Host ID Rack UN 188.8.131.52 120.97 KB 256 ? c84b80ea-cb60-422b-bc72-fa86ede4ac2e RACK1 UN 184.108.40.206 109.54 KB 256 ? 129087eb-9aea-4af6-92c6-99fdadb39c33 RACK1 UN 220.127.116.11 104.94 KB 256 ? 0540c7d7-2622-4f1f-a3f0-acb39282e0fc RACK1 Datacenter: ASIA-DC ======================= Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- Address Load Tokens Owns Host ID Rack UN 18.104.22.168 109.54 KB 256 ? c7686ffd-7a5b-4124-858e-df2e61130aaa RACK1 UN 22.214.171.124 109.75 KB 256 ? 39798227-9f6f-4868-8193-08570856c09a RACK1 UN 126.96.36.199 128.33 KB 256 ? 7a4957a1-9590-4434-9746-9c8a6f796a0c RACK1 Datacenter: EUROPE-DC ========================= Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- Address Load Tokens Owns Host ID Rack UN 188.8.131.52 114.35 KB 256 ? 4c3e1533-1b78-45bf-8bd4-818090f019ab RACK1 UN 184.108.40.206 109.54 KB 256 ? d99967d6-987c-4a54-829d-86d1b921470f RACK1 UN 220.127.116.11 109.54 KB 256 ? 2329c2e0-64e1-41dc-8202-74403a40f851 RACK1