[
https://issues.apache.org/jira/browse/NIFI-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047014#comment-15047014
]
ASF subversion and git services commented on NIFI-1271:
-------------------------------------------------------
Commit fb65cf1235d7a1176c58244bc4307f72de0e2a5d in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=fb65cf1 ]
NIFI-1271: Yield funnels and ports for nifi.bored.yield.duration amount of time
if backpressure is applied, as we do when there are no input FlowFiles.
Adjusting logic for ContinuallyRunProcessorTask#call in determining if there is
appropriate availability for processor relationships.
Signed-off-by: Aldrin Piri <[email protected]>
> Output Port of an inner process group has high CPU utilization when there is
> backpressure
> -----------------------------------------------------------------------------------------
>
> Key: NIFI-1271
> URL: https://issues.apache.org/jira/browse/NIFI-1271
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 0.3.0
> Reporter: Aldrin Piri
> Assignee: Mark Payne
> Priority: Minor
> Fix For: 0.4.0
>
> Attachments:
> 0001-NIFI-1271-Yield-funnels-and-ports-for-nifi.bored.yie.patch,
> NIFI-1271_-_Output_Port_CPU_Usage.xml
>
>
> Related to the template that drew out the issue with DistributeLoad in
> NIFI-1269, noticed that the computer was working fairly hard despite
> backpressure throughout the system effectively stopping processing/ingest.
> After going through the system, it seemed this was related solely to the
> output port of the process group. Toggling this directly went from near zero
> cpu usage to a much higher level of consumption.
> Will attach a template. To recreate, have the entirety of the processing
> path get backpressure to the point of ingest with GetFile. At this point,
> all components can be stopped. Toggling the Ingest File Stream output port
> will show the high level CPU usage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
