[
https://issues.apache.org/jira/browse/NIFI-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681908#comment-16681908
]
ASF GitHub Bot commented on NIFI-3229:
--------------------------------------
Github user patricker commented on the issue:
https://github.com/apache/nifi/pull/3131
@markap14 I was worried about the same thing, which is why the `if`
statement is structured as it is. First, we do the standard check on
`isActiveQueueEmpty`. This happens in the code now as you mentioned, and right
now if this passes we create a writelock update the queue and call the
processor.
All my change does is add one additional check, but only if the queue is
not empty. So as far as I can tell, I'm locking one extra time for a queue that
is already going to get locked, but not locking any queues that would not
already get locked. Also, because I'm updating the queue during my check, when
the processor does get called the lock should not last as long as it would
otherwise, as there is less work to do. So overall lock time should be affected
only minimally. Thoughts?
> 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)
