*Hello. Relatively new NiFi developer here. I have a question borne from my
lack of experience. Can anyone offer any guidance? *

*If a flowfile fails in a processor - let's say a Put File fails because of
underlying disk device failure - how do I replay the original flowfile(s)?
I need to understand how I resubmit the many files that would fail if, over
the course of a weekend, the disk device fails. Logging an attribute for an
error condition is a good start, but more important is resubmitting the
body of flowfiles when I get in Monday morning and reconcile the degraded
disk condition.*

*Generally speaking, is it considered a good practice or a bad practice to
feed back into a processor all its failure condition flowfiles? I'm
concerned that this would lead to a bottleneck or race condition that could
quickly snowball if failed flowfiles are just fed back into the processor
continuously. What can I do to mitigate such a circumstance? What is
considered NiFi "best practice" to handle such failures?*



*Apologies if this is not the proper venue to ask, and appreciate any
redirection advice. Am just starting to learn the ropes.*

*Thanks very much.*

Reply via email to