Cloudera Docs

Before you begin

Before you start the migration process, there are a few essential things to take care of. This section provides the key steps and requirements you should consider before migrating your NiFi dataflows and NiFi Registry versioned flows from an HDF 3.5.x or CFM 1.1.0 standalone cluster to a CFM 2.0.1 cluster on CDP Private Cloud Base.

CFM migration and upgrade options

When considering the transition to CFM 2.0.1, you have two main options:

Upgrade
It refers to a complete in-place upgrade of CFM on CDP Private Cloud Base. For detailed upgrade instructions, see the Upgrade Guide.
Migration
This method entails moving existing HDF cluster workloads to a fresh installation of CDP Private Cloud Base.

Migration paths

You must migrate your flows from one of the following environments:

  • HDF 3.5.x

    • Standalone (not managed by Ambari)
    • Ambari (with or without Ranger)
    • + HDP 3.1.5 and Ambari (with or without Ranger)

  • CFM 1.1.0

    • Standalone (not managed by Cloudera Manager)

Additional requirements

  • Align your HDF 3.5.x or CFM 1.1.0 standalone migration with an equivalent target environment.

    For example:

    • From HDF 3.5.x without Ranger to CFM 2.0.1 without Ranger
    • From HDF 3.5.x with Ranger to CFM 2.0.1 with Ranger
    • From CFM 1.1.x without Ranger to CFM 2.0.1 without Ranger
  • Ensure that:

    • You have deployed a CDP Private Cloud Base cluster with the necessary services running (ZooKeeper, Ranger, and similar) and default configurations in place.

    • You have sufficient networking connectivity and capacity between the source and destination clusters.

    • You have the necessary permissions to access and modify files on cluster nodes.

    • You have reviewed the Cloudera Flow Management Release Notes and are aware of the existing known issues.

    • You have reviewed the Apache NiFi Migration Guidance and Apache NiFi Registry Migration Guidance and understand any distinctions between source and destination components.