[
https://issues.apache.org/jira/browse/NIFI-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653767#comment-16653767
]
Peter Wicks commented on NIFI-4805:
-----------------------------------
[~bdesert] I don't disagree that there is a strong use case for a Retry
processor. The funny thing is, in my case the FlowFile hasn't even failed... I
just really want to delay it before it runs.
I think there is a need for two distinct processors. One that lets you penalize
any FlowFile, in line with what I've written for the PenalizeFlowFile, and a
Retry processor (NIFI-3792?).
If nobody minds, I'll link NIFI-3792 to this ticket, and add the Retry
processor as well. [~bdesert], I think you've provided a really good list of
requirements, and I'll work from that.
> allow delayed transfer
> ----------------------
>
> Key: NIFI-4805
> URL: https://issues.apache.org/jira/browse/NIFI-4805
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Martin Mucha
> Assignee: Peter Wicks
> Priority: Minor
> Attachments: retry.xml
>
>
> Nifi has concept of penalization, but this penalization has fixed delay, and
> there isn't way how to change it dynamically.
> If we want to implement retry flow, where FlowFile flows in loop, we can
> either lower performance of Processor via yielding it, or we can do active
> waiting. And this is actually recommended as a correct way how to do that.
> It seems, that we can easily implement better RetryProcessor, all we missing
> is `session.penalize` which accepts `penalizationPeriod`. Processor then can
> gradually prolong waiting time after each failure.
>
> Would it be possible to make such method visible?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
