[ 
https://issues.apache.org/jira/browse/NIFI-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654133#comment-16654133
 ] 

ASF GitHub Bot commented on NIFI-4805:
--------------------------------------

Github user patricker commented on the issue:

    https://github.com/apache/nifi/pull/3078
  
    I'm confused by your message @joewitt. I understand, "Yes, make it a delay 
processor". But then you mention `penalize` a lot of times. My thought was if 
it's a delay processor then it wouldn't ever call Penalize, but just not pass 
FlowFile's through to the next queue until the appropriate amount of time had 
passed.


> 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)

Reply via email to