@Raj B The PutHDFS will "close" the file after each append. The writing of a file every minute will be less efficient than say writing a bigger file every ten minutes, but that is something you will have to determine which is more important to your use case. But even just waiting a minute is still more efficient then writing 100 files a sec. ... View more

Looks like it might just have been a typo between "flowFile" and "flowfile" ... View more

Hi, Could you please let me know how the resetting of target signal count in wait processor work? Refer my question: https://community.hortonworks.com/questions/138762/reset-of-target-signal-count-in-wait-processor.html Thanks, John ... View more

Thank you very much ... View more

@Wynner Atlast !! Yeah!! Thanks a ton! ... View more

@Harish S I am glad you were able to correct the issue by configuring the correct KDC server in the jaas.conf file. ... View more

@Avish Saha Some processors work in NiFi FlowFiles in batches. In your case one of the FlowFiles is failing to match on the regex which is causing a session roll back of the entire session. Also seeing as how the processor reports 8,000,000+ tasks in the last 5 minutes, it does not look like it is penalizing that one bad FlowFile. While all FlowFiles routed to a "failure" relationship are penalized, this is not true for all processors when a session rollback occurs. ... View more

This issue is not limited to IE. A similar issue with cached credentials/session may occur in Chrome. Restarting Chrome resolves the issue as well. To restart Chrome without losing current tabs, type chrome://restart in a new tab. ... View more

@Peter Murray That is one way to configure it. The batching of 50 flow files is how the MonitorActivity processor works, no matter what Scheduling Strategy is implemented. I would change the Scheduling Strategy to Timer driven, and have it run once a minute, with the Threshold Duration to 24 hours, as you suggested. ... View more