Nikhil, Are you running a NiFi cluster or a single/standalone node?
If you're running standalone, state is stored locally on disk. By default, it is stored in ./state/local and so you'll want to ensure that you copy over the state/ directory from your previous install to the new install or otherwise update your state-management.xml file to point to the same directory that lives outside of nifi. I.e., copying this file over from your old install to the new install, by default, points to a directory within the nifi installation, so you'll want to provide the fully-qualified path to the directory or copy the directory over from the old install. If you are running in a cluster, then you'll want to ensure that you are pointing to the same ZooKeeper instance. If you're running an embedded ZooKeeper, you'll need to ensure that you copy over the ./state/zookeeper directory from your old installs to your new installs to ensure that the ZooKeeper data is kept up-to-date. Thanks -Mark On Aug 28, 2018, at 3:41 AM, Nikhil Chaudhary <[email protected]<mailto:[email protected]>> wrote: Hi, Has anyone else faced an issue when upgrading NiFi from 1.4.0 to 1.7.1, the ListS3 processor gets defaulted and it starts downloading everything all over again within that S3 bucket? The state management file mentioned at nifi.state.management.configuration.file was kept intact. Is there some other configurations that we need to be aware of to keep the state as-is and only continue onwards? Thank You. Best Regards, Nikhil C.
