Upgrading from DataStax Community 1.0.x/1.1 to DataStax Enterprise 2.2.x on RHEL-based Distributions¶

Upgrading a Node¶

Perform these upgrade steps on each node in the cluster. If the cluster is a mixed workload cluster, upgrade in the order described in Order of Upgrading Nodes. Complete all steps on one node before starting to upgrade the next node.

To upgrade a node

1. Remove dependencies on the old version of the package:

   rpm -e apache-cassandra1 –noscripts
   

   The old Cassandra configuration file is renamed to cassandra.yaml.rpmsave as shown in the output of this command.

   warning: /etc/cassandra/default.conf/cassandra.yaml
   saved as /etc/cassandra/default.conf/cassandra.yaml.rpmsave
   

2. Open the yum repository file for DataStax in /etc/yum.repos.d for editing.

   sudo vi /etc/yum.repos.d/datastax.repo
   

3. Replace the contents of the file with the following lines:

   [datastax]
   name= DataStax Repo for Apache Cassandra \
     baseurl=http://<username>:<password>@rpm.datastax.com/enterprise
   enabled=1
   gpgcheck=0
   

4. Upgrade the node.

   sudo yum clean all
   sudo yum install dse-full
   

   A prompt informs you of the download size and asks for confirmation to continue. For example:

   Total download size: 252 M
   Is this ok [y/N]: y
   

5. Type y.

6. Configure the upgraded node as described in the next section.

To configure the upgraded node

1. Open the old, renamed configuration file.

   vi /etc/cassandra/default.conf/cassandra.yaml.rpmsave
   

2. Open the new configuration file for editing.

sudo vi /etc/dse/cassandra/cassandra.yaml

3. Diff the new and old cassandra.yaml files.
4. Merge the diffs by hand from the old file to the new one except do not merge the snitch setting.
5. Configure the snitch setting and complete the upgrade as described in Completing the Configuration and Starting Up the Upgraded Node.