Configure Cassandra Cluster

Configure Cassandra for the Backend Server "seed" node

Start

1. For each Backend Server, open the the backend/etc/cassandra.yaml file with a text editor;
2. Edit the specified strings:

listen_address: <backend-node_ip_address>
rpc_address: 0.0.0.0
initial_token: 0 
seeds_provider:
- seeds: "<backend-node_ip_address>"

.

End

Next Steps

• Configure Cassandra for the Backend Server "non-seed" nodes

Configure Cassandra for the Backend Server "non-seed" nodes

Start

1. For each Backend Server, open the backend/etc/cassandra.yaml file with a text editor.
2. Edit the specified strings:

   listen_address: <node_ip_address>
   rpc_address: 0.0.0.0
   initial_token: <initial token for this node>
   seeds_provider:
                   - seeds: "<seed-backend-ipaddress>"
   

Note:

• If you want to add more than two servers, you must recalculate all initial tokens. See http://www.datastax.com/docs/0.8/install/cluster_init#token-gen-cassandra.
• When adding a new node to the Cassandra cluster, you must reconfigure all of the nodes in the cluster. Genesys recommends that you calculate the capacity of the cluster. The Cassandra cluster works with N / 2 +1 operating units and more, where N is the number of nodes of the Cassandra cluster.

Confirm that the following parameters point to the correct paths:

• data_file_directories — For example, C:\WebME Cluster\Node1\backend\storage\data
• commitlog_directory — For example, C:\WebME Cluster\Node1\backend\storage\commitlog
• saved_caches_directory — For example, C:\WebME Cluster\Node1\backend\storage\saved_caches

End

The following shows a sample configuration with two servers:

• Backend Server Seed Node

listen_address: 135.225.51.148
rpc_address: 0.0.0.0
initial_token: 0 
seeds_provider:
                - seeds: "135.225.51.148"

• Backend Server Non-seed Node

listen_address: 192.168.3.103
rpc_address: 0.0.0.0
initial_token: 85070591730234615865843651857942052864
seeds_provider:
                - seeds: "135.225.51.148"

Next Steps
Configure Rules Deployment for the Cluster