UpgradePDF version

Upgrading to CFM 2.1.4 from CFM 2.x

This section describes the steps of the upgrade process from CFM 2.x to CFM 2.1.4. To upgrade to CFM 2.1.4, 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.

  • You have upgrade Cloudera Manager and CDP Private Cloud Base if needed.

  • You have reviewed Upgrade Paths to be sure you are performing the right upgrade for your use case.

  • You have reviewed the following information in Before you upgrade are sure that you have met the pre-requites.

    • CFM migration and upgrade options
    • Upgrade paths
    • Supported CDP Private Cloud Base cluster versions
  1. Stop the NiFi and NiFi Registry services, 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 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.4 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.