To upgrade from CFM 2.0.1 to CFM 2.0.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 reviewed the following Before you upgrade information and are
sure that you are performing the right upgrade for your use case.
- CFM migration and upgrade options
- Upgrade paths
- Supported CDP Private Cloud Base cluster versions
-
Stop the NiFi and NiFi Registry services, in this order.
-
Delete the old CSD files.
-
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.
-
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.0.4 parcel.
After clicking Activate, the Activate CFM
2.0.4.0 on <cluster-name> pop-up displays. Click
Activate Only, and then
OK.
-
Restart NiFi and NiFi Registry and deploy the client configurations.
-
Optionally, to clean up, remove the 2.0.1.0 parcels from the host.
-
From the Parcel menu, go to the CFM 2.0.1.0
parcel.
-
Select Remove From Host.
-
Select Delete.