I know we have this issue in nifi 1.5 thought fixed in 1.9 . not sure in which version this is fixed?
Any thoughts? instead of a workaround , interested to know if this is handled in any newer versions?
I believe this is fixed in 1.9 (and up)
The bug jira https://issues.apache.org/jira/browse/NIFI-5849 addressed listSFTP and ListFTP losing state on a NiFi restart. This bug fix is included in Apache NiFi 1.9.0+ releases.
Since HDF 184.108.40.206 is based off Apache NiFi 1.9, you will have this fix.
Another possible reason for what you are seeing may be the result of using the "Tracking Entities" listing strategy in the ListFTP processor. This strategy requires that you have also configured a "Entity Tracking State Cache". If you use the DistributedMapCache embedded in your NiFi and you have not configured a "Persistence Directory" for the DistributedMapCacheServer, then all cache entries will be lost on a NIFi restart. This can lead to files being listed again on restart as the DistributedMapCacheServer in heap memory cache is populated all over again. If you setup the "Persistence Directory", then previously cached entries will be loaded back in to heap memory on NiFi restart.
Hope this helps,