Page History

These instructions assume:

• Your current installation is a NiFi cluster with an external Zookeeper.

• The FlowFile and Content Repositories are stored on separate drives as recommended in the NiFi System Administrator’s Guide (https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#flowfile-repository).

Note:

• You cannot have nodes with different NiFi versions in the same cluster.

• Running multiple NiFi nodes on the same host machine is highly discouraged.

Release Notes & Migration Guidance

...

You should review the Release Notes carefully to ensure that you understand the changes made and the impact they may have on your existing data flows and/or environment.

These The instructions below are general steps to follow when upgrading from one 1.x.0 release to another.  Check the Migration Guidance page for specific items that you should be aware of when moving between versions.

Note:

...

NiFi versions

...

.

...

Running multiple NiFi nodes on the same host machine is highly discouraged.

Before you begin

Before you begin, you can perform some tasks to improve the efficiency and success of your upgrade.

...

If you have written any custom NARs, first test and validate them in a separate desired release NiFi release sandbox prior to upgrading.  The verified NARs can be preserved during the upgrade by storing them in a centralized location.

1. Create a second library directory, called custom_lib.

2. Move your custom NARs to this new lib directory.

3. Add a new line to the nifi.properties file to specify this new lib directory:

nifi.nar.library.directory=./lib

nifi.nar.library.directory.custom=/opt/configuration_resources/custom_lib

Preserving your modified NARs

...

1. Identify and save the changes you have made to the default NAR files in your current instance.

2. Perform your upgrade to the desired NiFi release.

3. Redo the changes you have made to the NAR files in your new instance.

Installation

The instructions below assume:

...

Your current installation is a NiFi cluster with an external Zookeeper.

...

• https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#flowfile-repository

1. Download and extract the new NiFi tar.gz file.

2. For each node in your cluster, install the desired NiFi in parallel with your existing NiFi installation.  Assuming you have installed into an opt/ directory, for example:

Host Machine - Node 1

|--> opt/

   |--> 1.5.0-nifi

   |--> 1.6.0-nifi

 

Host Machine - Node 2

|--> opt/

   |--> 1.5.0-nifi

   |--> 1.6.0-nifi

Host Machine - Node 3

|--> opt/

   |--> 1.5.0-nifi

   |--> 1.6.0-nifi

 

Note:  Make sure that all file and directory ownerships for your new NiFi directories match what you set on the previous version.

...

• Shutdown your existing NiFi instance(s).

4. Use the <path to existing>/nifi/conf/ files to configure the corresponding files in your <path to new>/nifi/conf/ files of the same names.

Note:  If you are encrypting sensitive component properties in your dataflow via the sensitive properties key in nifi.properties file, make sure the same key is used when copying over your flow.xml.gz.  If you need to change the key, use the flow migration procedure and the NiFi Encrypt-Config Tool to produce a new flow.xml.gz file from the existing one.

5. Configure/confirm that your new instances point to the appropriate FlowFile, Content and Provenance repositories via the directory settings in the nifi.properties file.

6. To maintain state in your processors, copy the old local state directories to your new NiFi directories.  If you are also setting up a new external ZooKeeper, see the ZooKeeper Migrator section of the NiFi System Administrator’s Guide for instructions on how to move ZooKeeper information from one cluster to another and migrating ZooKeeper node ownership.

...