Warnings and prerequisites

Preparing Cloudera Search in your CDH cluster for an upgrade is a complex task.

warning

If your CDH 5.x cluster used SolrCell with Morphlines to index data to Solr, you can only upgrade to CDP 7.1.6 or higher.

The SolrCell version shipped with Cloudera Runtime 7.1.6 no longer contains the dateFormats field. As Solr is still able to convert most strings to dates, it is possible that removing the dateFormats field from your Morphlines is enough.

If you want to explicitly add a specific date format, Cloudera suggests one of the options in the following example.

To replace dateFormats : [ "MM-dd-yyyy" ]

You can either add the following to Morphlines for all the affected date fields:

{{convertTimestamp

{ field : document_header2 inputFormats : ["MM-dd-yyyy"] }
}}

or you can change the solrconfig.xml file, by adding the <str>MM-dd-yyyy</str> date format:

<updateProcessor class="solr.ParseDateFieldUpdateProcessorFactory" name="parse-date">
    <arr name="format">
      <str>MM-dd-yyyy</str>
      <str>yyyy-MM-dd['T'[HH:mm[:ss[.SSS]][z</str>
      <str>yyyy-MM-dd['T'[HH:mm[:ss[,SSS]][z</str>
      <str>yyyy-MM-dd HH:mm[:ss[.SSS]][z</str>
      <str>yyyy-MM-dd HH:mm[:ss[,SSS]][z</str>
      <str>[EEE, ]dd MMM yyyy HH:mm[:ss] z</str>
      <str>EEEE, dd-MMM-yy HH:mm:ss z</str>
      <str>EEE MMM ppd HH:mm:ss [z ]yyyy</str>
    </arr>
  </updateProcessor>

Prerequisites

Make sure you are running Cloudera Manager 7.1 or higher.
If you use Apache Sentry with policy files, you must transition to Sentry service before the upgrade.
Stop making changes to your Cloudera Search environment. Make sure that no configuration changes are made to Cloudera Search for the duration of the transition and upgrade. This includes adding or removing Solr Server hosts, moving Solr Server roles between hosts, changing hostnames, and so on.
Plan for an outage for any applications or services that use your Search deployment until you have completed re-indexing after the upgrade.
If you use Kerberos, create a jaas.conf file for the Search service superuser (solr by default).
If you are using the Lily HBase Indexer service, stop writing to any tables that are indexed into Solr, and stop the Lily HBase Indexer service (Key-Value Store Indexer service > Actions > Stop).
Do not create, delete, or modify any collections for the duration of the transition and upgrade.

You can continue indexing to existing collections (except Lily HBase indexing) until otherwise instructed.