[
https://issues.apache.org/jira/browse/NIFI-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581050#comment-16581050
]
Mark Payne commented on NIFI-4805:
----------------------------------
[~alopresto] I agree - as I mentioned in the PR, after I thought about this
more, I concluded that it was a pretty reasonable ask. I do think it should be
named {{Penalize}} or {{PenalizeFlowFile}}, as that's the NiFi terminology that
we use. I would be sure to store that 'counter' as an attribute instead of
attempting to maintain any state in the processor. That can get a bit tricky,
though, because we want to ensure that we could have a Penalize processor at
one point in the flow and another one down the line. So the attribute may need
to be named something like 'penalization.count.\{processor uuid}'. Even then,
though, there are likely some corner cases to consider... just something to
keep in mind.
> 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)
