[
https://issues.apache.org/jira/browse/NIFI-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653790#comment-16653790
]
Ed Berezitsky edited comment on NIFI-4805 at 10/17/18 4:29 PM:
---------------------------------------------------------------
[~patricker],
if you go with two processors solution - then I would suggest to remove
"retryAttrName" from PenalizeFlowFile Processor implementation. Because you
indeed do not implement retry. So that was misleading in the code.
was (Author: bdesert):
[~patricker],
if the you go with two processors solution - then I would suggest to remove
"retryAttrName" from PenalizeFlowFile Processor implementation. Because you
indeed do not implement retry. So that was misleading in the code.
> 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)
