Teamwork Cloud no longer supports Apache Cassandra 3.x, therefore before upgrading Teamwork Cloud, you need to upgrade Casandra to version 4.x (we recommend using Cassandra 4.0.3). | Note |
|---|
| - Make sure that all the nodes are ready.
- Create a snapshot of your data for backup.
- Upgrade sstables by running the command nodetool upgradesstables on each node.
|
To upgrade Cassandra
IMPORTANT! Flush memtables to the disk by executing the following command: | Code Block |
|---|
| language | bash |
|---|
| theme | DJango |
|---|
| linenumbers | true |
|---|
| nodetool drain |
Shut down the 3.x node. - Backup the Cassandra configuration file at: /etc/cassandra/default.conf/cassandra.yaml
Make a note of the existing cluster name and token count with the following command: | Code Block |
|---|
| language | bash |
|---|
| theme | DJango |
|---|
| linenumbers | true |
|---|
| grep -E 'num_tokens:|cluster_name:' /etc/cassandra/default.conf/cassandra.yaml |
Uninstall/remove Cassandra 3.x (example with yum package manager) | Code Block |
|---|
| language | bash |
|---|
| theme | DJango |
|---|
| linenumbers | true |
|---|
| sudo yum remove -y cassandra |
- Install Cassandra 4.x. for installation instructions, see Installing Cassandra on Linux or Installing Cassandra on Windows.
Configure the 4.x node to point to the appropriate data files in the /etc/cassandra/default.conf/cassandra.yaml settings as shown in the example below. | Code Block |
|---|
| data_file_directories:
- /data/data
commitlog_directory: /logs/commitlog
hints_directory: /data/hints
saved_caches_directory: /data/saved_caches |
Check the cluster name and token count in cassandra.yaml. If needed, replace the default values with the values set in 3.x. The example below shows the default values for a Cassandra 4.x installation. | Code Block |
|---|
| cluster_name: 'Test Cluster'
num_tokens: 16 |
| Note |
|---|
| title | Cassandra 4 Configuration |
|---|
| The cluster name and token count must match those values set in Cassandra 3.x. |
- Start the Cassandra 4.x node.
- Check the log files for errors.
- After the upgrade is complete, perform required post-installation configuration changes. For more information, see Post-installation steps on Linux or Post-installation steps on Windows.
| 