You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2015/12/08 04:07:10 UTC

[jira] [Commented] (NIFI-1271) Output Port of an inner process group has high CPU utilization when there is backpressure

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

Mark Payne commented on NIFI-1271:
----------------------------------

[~aldrin] - I can replicate the issue. I have an idea of what the problem likely is and will try to address in the morning. I think it is similar to the problem that we had a while back where Funnels did something similar.


> 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
>            Priority: Minor
>         Attachments: 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)