You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Peter Wicks (JIRA)" <ji...@apache.org> on 2018/10/17 16:06:00 UTC

[jira] [Commented] (NIFI-3792) A processor to facilitate retrying FlowFiles

    [ https://issues.apache.org/jira/browse/NIFI-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653771#comment-16653771 ] 

Peter Wicks commented on NIFI-3792:
-----------------------------------

[~JPercivall] I'm planning to work on this under NIFI-4805. Looks like you've had the ticket assigned since creation about 1.5 years ago. Hope that's not an issue?

> 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)