• Glossary
  • Support
  • Downloads
  • DataStax Home
Get Live Help
Expand All
Collapse All

DataStax Enterprise Upgrade Guide

    • About upgrading
    • Supported & compatible versions
    • Upgrading DSE
      • Planning your DSE upgrade
      • Upgrades for patch releases
        • 6.8.x patch releases
        • 6.0.x patch releases
        • 5.1.x patch releases
        • 5.0.x patch releases
        • 4.8.x patch releases
      • Upgrading DSE 6.7 to 6.8
      • Upgrading DSE 6.0 to 6.8
      • Upgrading DSE 5.1 to 6.8
      • Upgrading DSE 5.0 to 6.8
      • Upgrading DSE 5.0 to 5.1
      • Upgrading from DataStax Installer
        • Converting to Yum installation on RHEL-based systems
        • Converting to APT installation on Debian-based systems
        • Converting to binary tarball installation
      • Upgrading to earlier versions
        • Upgrading DSE 5.1 to 6.0
        • Upgrading DSE 5.0 to 6.0
        • Upgrading to DSE 5.0
          • Upgrading from DSE 4.7 to 4.8
        • Upgrading to DSE 4.7 or 4.8
        • Upgrading to DSE 4.6
        • Upgrading to DSE 4.0 or 4.5
        • Upgrading to DSE 3.2
          • Upgrading from DSE 3.0 to 3.2
          • Upgrading from DSE 2.2 to 3.2
        • Upgrading 5.1 using the DataStax installer
      • Backing up and restoring DSE
        • Backing up a package installation
        • Backing up a tarball installation
        • Restoring a DSE package installation from backup
        • Restoring a DSE tarball installation from backup
    • Upgrading Apache Cassandra
      • Upgrading Apache Cassandra to DSE
      • Upgrading Apache Cassandra
    • Upgrading OpsCenter
      • Before upgrading OpsCenter
      • DSE OpsCenter upgrade instructions
        • Upgrading package installations
        • Upgrading tarball installations
        • Upgrading when failover is enabled
        • Upgrading DataStax Agents
    • Upgrading DataStax Studio
    • Upgrading the DataStax AMI
  • DataStax Enterprise Upgrade Guide
  • Upgrading OpsCenter
  • Before upgrading OpsCenter

Before Upgrading DSE OpsCenter

For any major release, review the changes in features, configuration files, metrics, and APIs impacting upgrades to OpsCenter.

DataStax strongly recommends upgrading to the most recent version of OpsCenter 6.8 for DSE 6.8, and DSE 5.1. Upgrading to this version ensures that you take advantage of new and improved features, enhanced performance, and fixed bugs or known issues.

OpsCenter versions 6.8.0 through 6.8.3 do not support DSE 5.1.x. Support for DSE 5.1.x is available in OpsCenter 6.8.4 and later.

See New features (6.8) for a description of features added in each OpsCenter release. See also OpsCenter compatibility with DSE.

Upgrade Considerations

Before upgrading to OpsCenter, carefully consider the following changes and follow any prescribed actions.

Support for Multiple User Roles using LDAP Authentication

Users can have multiple roles when using LDAP authentication. If the list of a user’s groups map to more than one role in OpsCenter, each user is granted each of the listed roles, and their resulting OpsCenter permissions are merged for all of their roles. See Adding a role for an LDAP user (6.8).

In OpsCenter 6.1.10 and later and OpsCenter 6.5.3 and later, you must update custom scripts and applications that use the OpsCenter API when using multiple user roles with LDAP authentication. If a custom script or application that uses the OpsCenter API did not account for multiple user roles, and a user has multiple roles, the script or application will fail because the role attribute cannot be found. The single role attribute is provided for users that have only one role. If your application or script has users with only one role, then updates are not required for continued use.

LCM Now Installs OpenJDK as the Default Option

Starting in January 2019, Oracle is ending public updates for the Oracle Java 8 runtime, requiring commercial users to purchase a paid license to obtain updates.

To simplify licensing, LCM in OpsCenter 6.7.0 introduces support for installing OpenJDK as the default option. LCM installs OpenJDK as distributed by operating system vendors through .deb or .rpm packages. Existing clusters are migrated to OpenJDK unless Oracle is explicitly selected as the Java vendor prior to running the first install or upgrade job from within OpsCenter 6.7.0.

To understand how this change effects your OpsCenter installation, see Choosing a Java vendor in Lifecycle Manager (6.8).

Upgrading OpsCenter DSE OpsCenter upgrade instructions

General Inquiries: +1 (650) 389-6000 info@datastax.com

© DataStax | Privacy policy | Terms of use

DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.

Kubernetes is the registered trademark of the Linux Foundation.

landing_page landingpage