[
https://issues.apache.org/jira/browse/NIFI-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089336#comment-17089336
]
Kirhold commented on NIFI-3229:
-------------------------------
I don't think it is an improvement but a bug. When there is penalized file in
incoming queue and processor's run schedule is set to 0, then CPU load is
significantly higher. As a workaround we set 10 sec per "small" processor, but
it is problematic for processors that has more incoming files and take one file
per run - then, we need keep 0sec.
I hope it can be resolved in future releases.
> When a queue contains only Penalized FlowFile's the next processor Tasks/Time
> statistics becomes extremely large
> ----------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-3229
> URL: https://issues.apache.org/jira/browse/NIFI-3229
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Dmitry Lukyanov
> Assignee: Peter Wicks
> Priority: Minor
> Attachments: flow.xml.gz, nifi-stats.png, nifi-stats2.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> fetchfile on `not.found` produces penalized flow file
> in this case i'm expecting the next processor will do one task execution when
> flow file penalize time over.
> but according to stats it executes approximately 10000-60000 times.
> i understand that it could be a feature but stats became really unclear...
> maybe there should be two columns?
> `All Task/Times` and `Committed Task/Times`
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
