[
https://issues.apache.org/jira/browse/NIFI-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341415#comment-16341415
]
Martin Mucha commented on NIFI-4805:
------------------------------------
I understand that, but retry-loop is valid usecase. There are event 'how-to's
on web implemented via just looping without any slowing down (active waiting).
Please give me resolution on this.
I don't want active waiting loop. I don't want to implement my own scheduler
either with persisting FlowFiles until their retry come. IIUC penalization is
the simplest correct way, once it exists. Or would you recomment something
else? (and if some devel abuses feature, it's his users who should suffer, not
other devels/users, no?)
> 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
> 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)
