Cloudera Docs

Upgrading to CFM 2.1.5

To upgrade from CFM 1.0.x to CFM 2.1.5, you need to upgrade to CFM 1.1.0 first. Then you must stop the CFM services, update the CSD files, restart the SCM Server, and activate the new CFM parcel.

If you are upgrading from CFM 1.0.0 or CFM 1.0.1, first you need to upgrade to CFM 1.1.0.

If you are upgrading from CFM 1.1.0 on CDH 6.x, perform the following steps.

For other upgrade scenarios, see Upgrade and migration paths.

Before you begin the CFM upgrade, ensure that you have completed the steps to:

  • Turn off TLS regeneration.
  • Back up your keystore and truststore settings for NiFi and NiFi Registry.
  1. Stop NiFi, NiFi Registry, and NiFi CA Service in this order.
  2. Delete the old CSD files.
  3. Download the new CSD files.
    The default CSD location is /opt/cloudera/csd, but you can configure that location from Cloudera Manager Administration | Settings | Local Descriptor Repository Path.

    Ensure that you maintain the appropriate file ownership and access attributes and SELinux permissions if needed.

  4. Download the new CFM parcel and .sha checksum file appropriate for your operating system.
    The default parcel location is /opt/cloudera/parcel-repo/.

    Ensure that you maintain the appropriate file ownership and access attributes and SELinux permissions if needed.

  5. Restart the cloudera-scm-server service: 
    service cloudera-scm-server restart
  6. In Cloudera Manager, from the Parcels page, distribute and activate the CFM parcel to which you want to upgrade.
    After clicking Activate, the Activate CFM <version-number> on <cluster-name> pop-up displays. Click Activate Only, and then OK.
  7. Optionally, to clean up, remove the older parcels from the host.
    1. From the Parcel menu, go to the older CFM parcel.
    2. Select Remove From Host.
    3. Select Delete.

Once you have completed the upgrade, perform the following additional tasks:

  • Set the keystore and truststore settings with the values from your backup.
  • Turn off identity mapping for both NiFi and NiFi Registry.
  • Start NiFi and NiFi Registry.
  • Optionally, you can remove the NiFi CA service.