Thanks for that information! Still trying to understand Nifi better. 1. SplitText (5000 'Line Split Count') -> SplitText (1 'Line Split Count') I added that, will see if that resolves the problem.
2. Usually breaks after running couple of hours, when content repository is full. I have disabled archiving, which should be fine in my case since reading data from persistent storage. 3. Events are very small, hardly 500 bytes. So actually after SplitText there are around hundred thousands of tiny flowfiles. 4. Is it necessary to promote the entirety of the content into a flow file attribute? I am directly not even using flowfile attributes, only using the content (these readymade processors I list are the only ones using it). Can still be a concern? or can I remove some part of flowfiles? 5. I know this can happen again, I want to be able to track which s3 files failed in case something breaks, so that I can replay them. Any integration for provenance repo to something like cloudwatch would have been great to monitor failed files. Is there any similar processor? Appreciate your help. -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Nifi-in-a-hung-state-tp14713p14724.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
