You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Denis Jakupovic (Jira)" <ji...@apache.org> on 2021/03/04 15:09:00 UTC

[jira] [Updated] (NIFI-8282) High CPU load when processor set on Primary Node Excecution with incomming connection

     [ https://issues.apache.org/jira/browse/NIFI-8282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denis Jakupovic updated NIFI-8282:
----------------------------------
    Summary: High CPU load when processor set on Primary Node Excecution with incomming connection  (was: High CPU load when set on Primary Node Excecution)

> High CPU load when processor set on Primary Node Excecution with incomming connection
> -------------------------------------------------------------------------------------
>
>                 Key: NIFI-8282
>                 URL: https://issues.apache.org/jira/browse/NIFI-8282
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.11.4, 1.13.0, 1.12.1
>         Environment: Docker Image
>            Reporter: Denis Jakupovic
>            Priority: Major
>              Labels: CPU, InvokeHTTP, load, primary
>
> Currently we use over 100 InvokeHTTP processors which are mostly in idle the whole time. The InvokeHTTP processors are triggered via an incomming connection, so they should do nothing until triggered.
> If set to primary we have a cpu load of 120-150% on 6 cores. When set on all nodes the cpu time drops to 20%.
> EDIT: This phenomena occurs if a processor is set to primary if it has an incomming connection. Tested on three processors, the CPU on 2 of 3 nodes went up to 120-150%.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)