Cloudera Docs

Upgrading to CFM 2.0.1

To upgrade from CFM 1.1.0 to CFM 2.0.1, you must stop the CFM services, update the CSD files, restart the SCM Server, and activate the new CFM parcel.

Cloudera recommends that you upgrade from CFM version 1.1.0 to 2.0.1

If you must upgrade from CFM version 1.0.x, you should first upgrade to CFM 1.1.0. For detailed instructions, see the Upgrade documentation for CFM 1.1.0.

Before you begin the CFM upgrade, make sure you have completed the following preparatory steps:

  • Disable TLS regeneration.
  • Back up your keystore and truststore settings for NiFi and NiFi Registry.
  1. Sequentially stop NiFi, NiFi Registry, and NiFi CA Service.
  2. Delete the old CSD files.
  3. Download the new CSD files.
    The default CSD location is /opt/cloudera/csd, but you can configure the location from Cloudera Manager Administration > Settings > Local Descriptor Repository Path.
  4. Download the new CFM parcel and .sha checksum file appropriate for your operating system.
    The default parcel location is /opt/cloudera/parcel-repo/.
  5. Restart the cloudera-scm-server service by running the following command: 
    service cloudera-scm-server restart
  6. In Cloudera Manager, navigate to the Parcels page, and distribute and activate the CFM parcel that you want to use.
    After clicking Activate, the Activate CFM 2.0.1.0 on <cluster-name> pop-up displays. ClickActivate Only > OK.
  7. Optional: you can clean up by removing the older parcels from the host.
    1. From the Parcel menu, go to the CFM parcel you do not need.
    2. Select Delete > Remove From Host.

Once the upgrade is complete, perform the following additional tasks:

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