• 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
  • Special steps for upgrades from DataStax Enterprise 4.0.0

Special steps for upgrades from DataStax Enterprise 4.0.0

Due to a bug in DataStax Enterprise 4.0.0, upgrading clusters with search nodes from DataStax Enterprise 4.0.0 to 4.0.x requires special steps to prevent data loss.

This bug impacts upgrades only from DataStax Enterprise 4.0.0.

DataStax is offering a complimentary half-day Upgrade Assessment. This assessment is a DataStax Services engagement designed to assess the upgrade compatibility of your existing DSE deployment to later DSE versions, including 5.1, 6.0, 6.7, and 6.8. Contact the DataStax Services team to schedule your assessment.

Procedure

  1. Drain each node in the cluster, but do not stop the node.

  2. Reload the Solr core.

    In the following example, the Solr core is wiki.solr running on the local host on port 8983.

    curl -X POST "http://127.0.0.1:8983/solr/admin/cores?action=RELOAD&name=wiki.solr&reindex=false&deleteAll=false"
  3. Upgrade the cluster.

  4. Reindex the Solr core.

    In the following example, the Solr core is wiki.solr running on the local host on port 8983.

    curl -X POST "http://127.0.0.1:8983/solr/admin/cores?action=RELOAD&name=wiki.solr&reindex=true"

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