Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

 

 

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

 

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

3. On your existing NiFi installation: 

 

  • Stop all processors responsible for ingesting new data.

...

 

  • Allow NiFi to run until no more FlowFiles are queued anywhere in the dataflow(s).

 

...

  • Shutdown your existing NiFi instance.

 

...

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. Specifically, copy over:

 

...

.

...

authorizations.xml

flow.xml.gz

nifi.properties

keystore.jks

truststore.jks

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.

 

7. Start each of your new NiFi instances.

 

 

8. Verify that:

 

 

  • All your data flows have returned to a running state. Some processors may have new properties that need to be configured, in which case they will be stopped and marked “invalid”.

 

 

  • All your expected controller services and reporting tasks are running again.  Address any controller services or reporting tasks that are marked "invalid".

 

...

9. After confirming your new NiFi instances are stable and working as expected, the old instances can be removed.