[
https://issues.apache.org/jira/browse/NIFI-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687117#comment-16687117
]
ASF GitHub Bot commented on NIFI-3229:
--------------------------------------
Github user patricker commented on the issue:
https://github.com/apache/nifi/pull/3131
@markap14 I built unit tests, but I'm having trouble running them at scale.
I temporarily checked back in the original method so I could run side-by-side
speed comparisons on the same `Connectable`. But if I exceed about 100k tests
my unit tests seem to go out to lunch, even if I increase heap so they don't
run out.
These are checked in right now to run 1 million iterations, but that has
not succeeded for me... This is true of the unmodified method if run by itself
also (at least on my poor little computer).
> 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
>
>
> 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
(v7.6.3#76005)
