To upgrade to CFM 2.1.5 from a lower 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.
You have upgraded Cloudera Manager and CDP Private Cloud Base if needed.
You have reviewed the Upgrade and migration paths to
make sure you are performing the right upgrade for your use case.
You have reviewed the Before you upgrade information to
make sure you meet the prerequisites.
Stop the NiFi and NiFi Registry services, in this order.
Delete the old CSD files.
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.5 SP3 on
RHEL7/CentOS7.
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.
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.
Restart the cloudera-scm-server service:
service cloudera-scm-server restart
In Cloudera Manager, from the Parcels page, distribute and
activate the CFM 2.1.5 parcel.
After clicking Activate, the Activate CFM
<version> on <cluster-name> pop-up displays. Click
Activate Only, and then
OK.
Restart Cloudera Management Service.
Restart NiFi and NiFi Registry and deploy the client configurations.
Optionally, to clean up, remove the previous parcels from the host.
From the Parcel menu, go to the older CFM
parcel.
Select Remove From Host.
Select Delete.
From the Ranger UI, NiFi service controller policy:
Add the nifi user to the policy with READ permissions.
