[
https://issues.apache.org/jira/browse/NIFI-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654143#comment-16654143
]
ASF GitHub Bot commented on NIFI-4805:
--------------------------------------
Github user bdesert commented on the issue:
https://github.com/apache/nifi/pull/3078
@joewitt , @patricker
While working on implementations, I faced a problem of penalization on
failure.
Some processors are penalizing FF on failure, some do only on rollback,
some gives you a choice whether to penalize or not on failure.
Use Case:
FetchFile -> transform -> PutHiveStreaming
On PutHiveStreaming failure -> 1) wait 1 min + retry, 2) create a table
(puthiveql will make you overwrite content, so you cannot do that sequentially).
There are more use, fo now I do like this:
> 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)
