This page provides instructions to set up a Teamwork Cloud (TWCloud) Cluster cluster on your system. A TWCloud Cluster Teamwork Cloud cluster is composed of two clustering layers , TWCloud – Teamwork Cloud and Cassandralayers.
To set up a TWCloud ClusterTeamwork Cloud cluster, you need to do perform two separate tasks:
Prior to establishing a Cassandra cluster, you need to determine the following.
The initial number of nodes in the cluster.
The IP address of each node.
Determine which node to will be the seed.
When setting up a Cassandra node, you need to configure a seed that indicates an initial contact point seed for the new node. So, you can configure the seed using the IP of any existing active node in the cluster. Use the node's own IP when configuring the first node. For example, if you are configuring a three-node cluster and the nodes' IPs are 10.1.1.101, 10.1.1.102, and 10.1.1.103. Select one, for example 10.1.1.101, as the seed. While you are configuring cassandra.yaml, specify 10.1.1.101 as the seed value for all of the three nodes.
After installing and configuring all nodes, start the seed node. Verify that it is operational by issuing the command "nodetool status".
Once the seed node is operational, you can proceed to start the other nodes in the cluster. You must allow the node to join the cluster before proceeding to the next node. After all nodes have started, the "nodetool status" command will display results as shown below.
Code Block
Datacenter: datacenter1
=======================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--
Address Load Tokens
Address Load Tokens Owns (effective) Host
ID RackUN
ID Rack
UN 10.1.1.
101
101 6.7
GB 256 35.1% b33c603a
GB 256 100% b33c603a-95c7-426d-9f7b-
ebad2375086a
ebad2375086a
rack1
UN
UN 10.1.1.
102
102 6.34
GB 256 32.5% 16f40503
GB 256 100% 16f40503-4a65-45fe-9ee7-
5d942506aa87
5d942506aa87
rack1
UN
UN 10.1.1.
103
103 6.15
GB 256 32.4% 2d90c119
GB 256 100% 2d90c119-08a4-4799-ac73-0440215d0b18
rack1
Note
title
Node Consistency
In order to ensure that all nodes are consistent, please run the "nodetool repair" command nightly. This can be scheduled as a crontab job or via Windows Task Scheduler. This only needs to be executed on a single node.
Anchor
twcloud
twcloud
Setting up a TWCloud Cluster
Before setting up a TWCloud Cluster, you need to determine the following.
The initial number of nodes in the cluster.
The IP address of each TWC node.
Prepare a list of IPs of Cassandra nodes.
The instructions below use the following sample environment for ease of understanding.
3 nodes TWC cluster
TWC node IP address are 10.1.1.111, 10.1.1.112, and 10.1.1.113
All nodes will be used as seed nodes
IP address of Cassandra nodes are 10.1.1.101, 10.1.1.102, 10.1.1.103
Setting up the TWCloud Cluster involves 2 groups of parameters in application.conf.
TWCloud clustering parameter
- akka.cluster.seed-nodes
This parameter indicates the initial contact points for the cluster.
If you install TWCloud using the installer file, you will be asked to provide the seed node IP during installation process and the value will be configured in application.conf.
If you install using the zip file, you will need to manually configure the parameter in application.conf. Search for the following:
.ip} with the IP addresses of the seed nodes, so it should look similar to the following: seed-nodes = ["akka://twcloud@10.1.1.111:2552","akka://twcloud@10.1.1.112:2552","akka://twcloud@10.1.1
.
113:2552"]
Cassandra configuration parameters
- esi.persistence.cassandra.connection.seeds
The value of this parameter is a list of Cassandra node IP addresses. You can find this parameter in application.conf by conf by looking for the following.
Code Block
title
application.conf
#
List
The list of comma-separated
delimited host
hosts.
#
Setting
Set the value
as
to
localhost
the
will
IP
be
addresses
resolved
of
from
Cassandra
InetAddress.getLocalHost().getHostAddress()# Ex
nodes.
# If one Cassandra node is used, set one seed, e.g. seeds = ["10.1.1.123"]
# If three cassandra nodes are used, set two seeds, e.g. seeds =["10.1.1.
124
123", "10.1.1.
125
124"]
- seeds
=
["localhost"]
As you can see, the default value is [“localhost”], which is only suitable for a single node server where both
TWCloud
Teamwork Cloud and Cassandra are deployed on the same machine. According to our sample environment, you should change it to the following.
This parameter defines the Cassandra replication factor
for the “esi” keyspace used by TWCloud. The replication factor
which describes how many copies of your data will be written by Cassandra. For example, replication factor 2 means your data will be written to 2 nodes.
For a three-node cluster, if you would like the cluster to be able to survive 1 node loss, you will need to set the replication factor to 3.
Code Block
persistence {
cassandra {
keyspace {
replication-factor = 3
cassandra {
keyspace {
replication-factor = 3
}
Please note that this configuration will be used only for the first time TWCloud Teamwork Cloud connects to Cassandra and creates a new esi twc keyspace. Changing the replication factor after the keyspace has already been created is rather a complex task. Read Read this document if you need to change it.
Note
TWCloud Teamwork Cloud uses QUORUM for both write and read consistency levellevels.
Click here for a detailed explanation about of data consistency.
To start up the TWCloud Teamwork Cloud cluster, first start the server on the seed machine and wait until you see a message similar to the following in the server.log.
INFO
Code Block
INFO 2017-02-15 10:57:08.409 Teamwork
TWCloud
Cloud
Cluster
cluster with 1 node(s) : [10.1.1.111] [com.nomagic.esi.server.core.actor.ClusterHealthActor, twcloud-esi.actor.other-dispatcher-31]
Then you can start the server on the remaining machines. You should see the following messages in the server.logwhich shows all 3 nodes are forming the cluster.
Code Block
INFO
INFO 2017-02-15 10:58:23.956 Teamwork
TWCloud
Cloud
Cluster
cluster with 2 node(s) : [10.1.1.111, 10.1.1.112] [com.nomagic.esi.server.core.actor.ClusterHealthActor, twcloud-esi.actor.other-dispatcher-18]
Before setting up a Teamwork Cloud cluster, you need to determine the following.
The initial number of nodes in the cluster.
The IP address of each Teamwork Cloud node.
Prepare a list of IPs of Cassandra nodes.
The instructions below use the following sample environment for ease of understanding.
3 nodes Teamwork Cloud cluster.
Teamwork Cloud node IP addresses are 10.1.1.111, 10.1.1.112, and 10.1.1.113.
All nodes will be used as seed nodes.
IP addresses of Cassandra nodes are 10.1.1.101, 10.1.1.102, 10.1.1.103.
Setting up the Teamwork Cloud cluster involves 2 groups of parameters in application.conf.
Teamwork Cloud clustering parameter
- akka.cluster.seed-nodes
This parameter indicates the initial seed for the cluster.
If you install Teamwork Cloud using the installer file, you will be asked to provide the seed node IP during installation process and the value will be configured in application.conf.
If you install using the zip file, you will need to manually configure the parameter inapplication.conf. Search for the following:
