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.

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"

Was this helpful?

Give Feedback

How can we improve the documentation?

© Copyright IBM Corporation 2025 | Privacy policy | Terms of use |  Manage Privacy Choices

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.

General Inquiries: Contact IBM