[
https://issues.apache.org/jira/browse/NIFI-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16343536#comment-16343536
]
Mark Payne commented on NIFI-4805:
----------------------------------
[~alfonz] - I'm sorry, I don't think I was clear on my concern. I am totally
okay with having a PenalizeFlowFile processor (in fact, that's exactly what i
would recommend calling it, in order to adhere to the standard naming
conventions. Or, perhaps, just Penalize). The only concern that I have is with
the the concept of introducing a new method overload to
ProcessSession.penalize(). I think we should keep the existing penalize()
method that exists and then have the new processor just penalize the FlowFile
and route to 'success'. Unless I am missing something, I think this does still
give you what you're looking for (the ability to delay processing of the
flowfile without introducing artificial delays with yield or 'active waiting'),
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)
