Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this page

Table of Contents
maxLevel5

Preparing to upgrade Cassandra

To prepare for Cassandra upgrade


  1. Ensure that all Cassandra nodes are ready. Run the following command and verify that all nodes are Up and Normal:
    Code Block
    languagebash
    themeDJango
    linenumberstrue
    nodetool status
  2. Leave the Cassandra service running but stop all Teamwork Cloud services.
  3. Back up your current database before upgrading.
  4. Upgrade all Cassandra data tables to current version by running the following command:
    Code Block
    languagebash
    themeDJango
    linenumberstrue
    nodetool upgradesstables
    Note

    This process can take a long time for large databases. To run the upgrade process in the background, you can use the Linux nohup command:

    Code Block
    languagebash
    themeDJango
    linenumberstrue
    nohup nodetool upgradesstables &

    Make sure this process is completed before proceeding!

Upgrading Cassandra

To upgrade Cassandra


  1. IMPORTANT! 

...

id1262020290

...

id1262020301

...

id1262020300

Teamwork Cloud no longer supports Apache Cassandra 3.x, therefore before upgrading Teamwork Cloud, you need to upgrade Casandra to version 4.1.

Note
titleBefore upgrading
  • 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

  1. Flush memtables to the disk by executing the following command:

    Code Block
    languagebash
    themeDJango
    linenumberstrue
    nodetool drain

...

  1. Stop the Cassandra service.

  2. Backup the Cassandra configuration file at: /etc/cassandra/default.conf/cassandra.yaml
  3. Make a note of the existing cluster name and token count with the following command:

    Code Block
    languagebash
    themeDJango
    linenumberstrue
    grep -E 'num_tokens:|cluster_name:' cassandra.yaml
  4. Uninstall/remove Cassandra

...

  1. (example with yum package manager)

    Code Block
    languagebash
    themeDJango
    linenumberstrue
    sudo yum remove -y cassandra
  2. Install

...

  1. new version of Cassandra (for installation instructions,

...

...

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
languagebash
titleExample
data_file_directories:
- /data/data
commitlog_directory: /logs/commitlog
hints_directory: /data/hints
saved_caches_directory: /data/saved_caches
  1. ).
  2. Check the cluster name and token count

...

  1. in cassandra.yaml. If needed, replace the default values with the values set in

...

  1. the previous version. The example below shows the default values for a Cassandra

...

  1. installation. 

  2. Code Block
    languagebash
    titleExample
    cluster_name: 'Test Cluster'
    num_tokens: 16
    Note
    titleCassandra 4 Configuration

    The cluster name and token count must match those values set in

...

  1. the previous version of Cassandra.

  2. Start the Cassandra

...

  1. service.
  2. Check if the service is running smoothly:

    • Check the log

...

    • file for startup errors.

...

    • Verify that all nodes have a status of Up and Normal with this command:

      Code Block
      languagebash
      themeDJango
      linenumberstrue
      nodetool status

...


Additional resources

For more information about upgrading Apache Cassandra, see https://www.datastax.com/learn/whats-new-for-cassandra-4/migrating-cassandra-4x.