Created 01-02-2017 09:05 AM
Created 01-02-2017 01:04 PM
@amanjain
The FlowFile would be rooted to the failure relationship in both those case. Those FlowFiles would be penalised based on the penalty duration configured on the fetchSFTP processor (default of 30 secs). That FlowFile will not be processed by the processor it is connected to until that penalty has expired. The common scenario her is to have the failure relationship loop back on the fetchSFTP processor so after penalty has expired another attempt will be made to retrieve the data.
Matt
Created 01-02-2017 01:04 PM
@amanjain
The FlowFile would be rooted to the failure relationship in both those case. Those FlowFiles would be penalised based on the penalty duration configured on the fetchSFTP processor (default of 30 secs). That FlowFile will not be processed by the processor it is connected to until that penalty has expired. The common scenario her is to have the failure relationship loop back on the fetchSFTP processor so after penalty has expired another attempt will be made to retrieve the data.
Matt
Created 01-03-2017 09:09 AM
@Matt Thanks Matt for the quick reply
Created 01-03-2017 02:46 PM
@Aman Jain If you found this information helpful,please accept the answer.
Created 10-19-2018 03:29 PM
Hi,
I have got some log messages like this when I cannot get a downloaded files (there's no errors flow: comms failed, not found, permission denied) .
I wonder whether this case related to the setting of "Data timeout" and "Connection timeout".
If you think so, please suggest, how can I deal with this problem? What if I put 0 sec to each parameter, does this mean no limit timeout?
Thank you
2018-10-18 08:59:50,661 INFO [Provenance Maintenance Thread-2] o.a.n.p.expiration.FileRemovalAction Removed expired Provenance Event file /nifi-repository-provenance/64054866.prov.gz