[
https://issues.apache.org/jira/browse/NIFI-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654116#comment-16654116
]
ASF GitHub Bot commented on NIFI-4805:
--------------------------------------
Github user patricker commented on the issue:
https://github.com/apache/nifi/pull/3078
@joewitt Originally I was going to write a processor that looked at how
long files had been queued and only moved them forward after the appropriate
time had elapsed, a true Delay processor. But when I found this existing JIRA
ticket, and since two other developers had discussed it quite a bit, I went
with building a Penalize processor.
The use case is absolutely causing a delay in the Flow. Would you prefer I
go back to something more like my original approach and only let FlowFile's
through based on their Queued times? This way would be more configurable, and
we could use an optional attribute/EL to decide how long they should be forced
to delay.
> 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)
