|Configuration file||Necessary changes|
|authorizers.xml||Copy the |
If you are using the default “file-provider” authorizer, ensure that you copy the
Configuration best practices recommend creating a separate location outside of the NiFi base directory for storing such configuration files. If you are storing these files in a separate directory, you do not need to move them. Instead, ensure that the new NiFi is pointing to the same files. For example:
Update the values based on values from the existing NiFi file.
|bootstrap.conf||Use the existing NiFi bootstrap.conf file to update properties in the new NiFi.|
|logback.xml||If you added any custom logging modification to the existing NiFi, make those same changes to the new NiFi.|
If you used a provider value in the existing NiFi, copy the
Use the existing file to populate the same properties in the new NiFi
This file contains the majority of NiFi configuration settings, so ensure that you have copied the values correctly.
If you followed NiFi best practices, the following properties should be pointing to external directories outside of the base NiFi installation path.
If the below properties point to directories inside the NiFi base installation path, you must copy the target directories to the new NiFi. Stop your existing NiFi installation before you do this.
If you have retained the default value, (
Alternately, you can copy to an external location and update the property value to point there.
Same applies as above if you want to retain archived copies of the
Best practices recommends that you use an external location for each repository. Point the new NiFi at the same external database repository location.
Best practices recommends that you use an external location for each repository. Point the new NiFi at the same external flowfile repository location.
Warning: You may experience data loss if flowfile repositories are not accessible to the new NiFi.
Best practices recommends that you use an external location for each repository. Point the new NiFi at the same external content repository location.
Your existing NiFi may have multiple content repos defined. Make sure the exact same property names are used and point to the appropriate matching content repo locations. For example:
Warning: You may experience data loss if content repositories are not accessible to new NiFi.
Warning: You may experience data loss may if property names are wrong or the property points to wrong content repository.
Best practices recommends that you use an external location for each repository. Point new NiFi at same external database provenance repository location.
Your existing NiFi may have multiple content repos defined. Make sure exact same property names are used and point to appropriate matching content repo locations. For example:
Note: You may not be able to query old events if provenance repos are not moved correctly or properties are not updated correctly.
For the “local-provider” value, verify the location of “state/local” directory.
If you have retained the default location (
Configuration best practices recommend that you move the state to an external directory like
For a NiFi cluster, the “cluster-provider” ZooKeeper “Connect String" should be using the same external ZooKeeper as the existing NiFi installation.
|For a NiFi cluster, make sure the “cluster-provider” ZooKeeper "Root Node" matches exactly the value you used in the existing NiFi.|
|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.|