[jira] [Commented] (NIFI-4805) allow delayed transfer

["Mark Payne (JIRA)" <ji...@apache.org>]

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

Mark Payne commented on NIFI-4805:
----------------------------------

[~alfonz] the delay that is imposed by the session penalization is controlled in the Processor's Settings configuration dialog. We did used to have a session.penalize method that allowed the developer to indicate a penalization period. As a result, developers typically would expose this configuration via a processor property. Or sometimes multiple properties - "Penalization Period for ABC", "Penalization Period for XYZ", "Penalization Period for This Other Thing". This ended up becoming confusing for users, because it was just more complicated to configure this, and every processor configured this differently. As a result, it was eventually removed all together and placed just on the Settings pane for the processor.

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