To upgrade DataStax Enterprise 1.x.x - 2.2.x to 3.0.x, 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 tarball release
Follow the instructions in Upgrading DataStax Community--tarball.
To upgrade a packaged release
Run the Yum (CentOS/RHEL/Oracle Linux) or Aptitude (Debian/Ubuntu) update commands.
Run the install commands shown in Installing the DataStax Enterprise package on Debian and Ubuntu or Installing the DataStax Enterprise package on RHEL-based distributions.
Start the first node.
Configure the node: Open the old cassandra.yaml. Open the new cassandra.yaml:
Diff the new and old cassandra.yaml files. Merge the diffs by hand from the old file to the new one except do not merge the snitch setting.
Configure and start the node.
A few configuration settings need to be made before completing the upgrade of a DataStax Enterprise or a DataStax Community node.
To configure and start the node
If you customized property files, other than the cassandra-topology.properties, update files by hand. Merge the settings of old property files, other than cassandra-topology.properties, into the new property files instead of overwriting the files. Users who overwrite property files, other than cassandra-topology.properties, have reported problems.
It is ok to overwrite the old with the new cassandra-topology.properties file as instructed in Configuring the snitch setting.
If necessary, upgrade any CQL drivers and client libraries, such as python-cql, Hector, or Pycassa that are incompatible with the new DSE version. You can download CQL drivers and client libraries from the DataStax web site.
The CQL utility is included in the DataStax Enterprise installation, so no upgrade of the CQL utility is necessary.
Restart client applications.
If you created column families using the default SizeTieredCompaction, continue to the next step. If you created column families having LeveledCompactionStrategy, scrub the SSTables that store those column families.
If you meet conditions for upgrading SSTables, upgrade SSTables now.