[
https://issues.apache.org/jira/browse/NIFI-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653829#comment-16653829
]
Peter Wicks commented on NIFI-3792:
-----------------------------------
Sure, thanks [~JPercivall]. We had a list of requirements put together from the
other ticket, could you look and see if it covers all of these also?
https://issues.apache.org/jira/browse/NIFI-4805?focusedCommentId=16653454&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16653454
If you need any help I'd be happy to make changes on top of what you have put
together.
> A processor to facilitate retrying FlowFiles
> --------------------------------------------
>
> Key: NIFI-3792
> URL: https://issues.apache.org/jira/browse/NIFI-3792
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Joseph Percivall
> Assignee: Joseph Percivall
> Priority: Major
>
> When dealing with processor failures in production, potentially related to
> network issues, the current best practice is to retry the flowfile a couple
> times before declaring it a failure[1]. This currently requires multiple
> processors and penalizing the flowfile isn't possible. Also if the flow is
> not fast enough, back-pressure can cause a livelocked state which requires
> manual intervention.
> A new processor should be added to not only encourage best practices but also
> offer configuration options to deal with un-optimal situations.
> [1]
> https://community.hortonworks.com/questions/77336/nifi-best-practices-for-error-handling.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
