DataStax Enterprise 2.1 Documentation

Upgrading to DataStax Enterprise 2.1

You can upgrade from these releases to DataStax Enterprise 2.1:

  • A previous release of DataStax Enterprise
  • Cassandra 0.7.10, 0.8.10, and 1.0.x

This following component version changes and other major changes are included in DSE upgrades:

Upgrade Changes
DSE 1.0, 1.0.x, or 2.0.x Cassandra updated to 1.0.10, DataStax OpsCenter to 2.1, Mahout 0.6 added

Making a Backup

Before upgrading, take a snapshot of the node to be upgraded to make a backup of the data. This optional, recommended step allows you to rollback to the previous version if necessary. Taking a snapshot is fast, especially if you have JNA installed. Taking a snapshot effectively consumes zero disk space until you start compacting the live data files again.

Order of Upgrading Nodes

Observe the following order for upgrading nodes in a mixed workload cluster:

Analytics: Jobtracker, remaining seeds, remaining task trackers Cassandra: Seeds, then remaining nodes Solr: Seeds, then remaining nodes

Upgrading from DataStax Enterprise 1.0 or Later to DataStax Enterprise 2.1

To upgrade from a previous DataStax Enterprise packaged release to DataStax Enterprise 2.1

  1. Run the Yum (CentOS/RHEL/Oracle Linux) or Aptitude (Debian/Ubuntu) update commands.
  2. Run the install commands shown in Installing DataStax Enterprise on CentOS, RHEL, and OEL Systems or Installing DataStax Enterprise on Debian and Ubuntu Systems.
  3. You can use a rolling restart. Repeat the upgrade procedures on the next node in the cluster, following instructions in Using a Rolling Restart. Monitor the log files for any issues.
  4. Validate the upgrade.

To upgrade from a previous DataStax Enterprise tarball release to DataStax Enterprise 2.1

Follow the instructions for Upgrading a Tarball Installation of DataStax Community 1.0.x to DataStax Enterprise 2.1.

Upgrading from Other Versions of Cassandra or DataStax Community to DataStax Enterprise 2.1

The procedures listed in the previous section are based on upgrading from DataStax Community 1.0.x to DataStax Enterprise 2.1. Generally, these procedures work for upgrading from other releases to DataStax Enterprise 2.1. Exceptions are:

  • To upgrade from Cassandra 1.1 or later or DataStax Community 1.1.x or later, contact DataStax Support for instructions.
  • To upgrade from a Brisk release, contact Support.
  • To upgrade from Cassandra 0.8 or earlier, refer to NEWS.txt.

Tapping NEWS.txt for Upgrading Information

NEWS.txt contains late-breaking information about upgrading from previous versions of Cassandra.

A NEWS.txt archive is installed in the following locations:

Tarball <install_location>/resources/cassandra

Package /usr/share/doc/dse-libcassandra*

NEWS.txt is also posted on the Apache Cassandra project web site.

Unpack NEWS.txt.gz. For example:

cd /usr/share/doc/dse-libcassandra-2.1.1
sudo gunzip NEWS.txt.gz

Take at look at the information that is pertinent to your old version if there is any. For example, to upgrade from some early versions, you might need to upgrade sstables.

Upgrading and Counter Columns

If you use counter columns, upgrading SSTables is highly recommended.

Tarball

<install_location>/bin/nodetool -h upgradesstables

Package or AMI

nodetool -h upgradesstables