Upgrade and migrationPDF version

Upgrading to CFM 2.1.6 from CFM 2.1.5

This guide outlines the prerequisites and steps for upgrading from Cloudera Flow Management (CFM) 2.1.5 to CFM 2.1.6. If you want to upgrade from other CFM 2.x versions, check the available upgrade paths in the Upgrade and migration paths diagram to identify the sequence of intermediate upgrades required to transition from your current CFM version to CFM 2.1.6.

  • Review the possible upgrade paths.

    Before starting your CFM upgrade, it is crucial that you review the available upgrade paths to ensure that you are performing the right upgrade for your use case.

    If you want to use CFM 2.1.6, you have the following options:
    • Upgrade from CFM 2.1.5 on CDP 7.1.7 to CFM 2.1.6 CDP 7.1.7
    • Upgrade from CFM 2.1.5 on CDP 7.1.8 to CFM 2.1.6 CDP 7.1.8
    • Upgrade from CFM 2.1.6 on CDP 7.1.7 to CFM 2.1.6 on CDP 7.1.8
    • Upgrade from CFM 2.1.6 on CDP 7.1.8 to CFM 2.1.6 on CDP 7.1.9

    For an overview of all available paths, see Upgrade and migration paths.

  • Upgrade Cloudera Manager and CDP Private Cloud Base, if needed.

To upgrade to CFM 2.1.6 from an earlier version of CFM on CDP Private Cloud Base, you must stop the CFM services, update the CSD files, restart the SCM Server, activate the new CFM parcel, and then restart your CFM services.
  1. Stop the NiFi and NiFi Registry services, in this order.
  2. Delete the old CSD files.
  3. Download the new CSD files for NiFi and NiFi Registry.
    For example: Use the following wget commands to download the required CSD files for CFM 2.1.6 SP1 on RHEL7/CentOS7.
    wget https://<username>:<password>@archive.cloudera.com/p/cfm2/2.1.6.1000/redhat7/yum/tars/parcel/NIFI-1.23.1.2.1.6.1000-47.jar 

wget https://<username>:<password>@archive.cloudera.com/p/cfm2/2.1.6.1000/redhat7/yum/tars/parcel/NIFIREGISTRY-1.23.1.2.1.6.1000-47.jar

    By default, Cloudera Manager stores CSD files in /opt/cloudera/csd. To change this location, go to Administration > Settings > Local Descriptor Repository Path.

    Make sure the files have appropriate ownership, access attributes, and SELinux permissions if applicable.

  4. Download the new CFM parcel and .sha checksums 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 2.1.6 parcel.
    After clicking Activate, the Activate CFM <version> on <cluster-name> pop-up displays. Click Activate Only, and then OK.
  7. Restart Cloudera Management Service.
  8. Restart NiFi and NiFi Registry and deploy the client configurations.
  9. Optionally, to clean up, remove the previous parcels from the host.
    1. From the Parcel menu, go to the older CFM parcel.
    2. Select Remove From Host.
    3. Select Delete.
  10. From the Ranger UI, NiFi service controller policy:
    1. Add the nifi user to the policy with READ permissions.
    2. Verify the nifi group is set in the policy.

We want your opinion

How can we improve this page?

What kind of feedback do you have?