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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.11.4, 1.13.0, 1.12.1
• Fix Version/s: 1.14.0, 1.13.1
• Component/s: Core Framework
• Labels: CPU InvokeHTTP load primary
• Environment: Docker Image
• Flags: Patch
• Assignee: Mark Payne
• Reporter: Denis Jakupovic
• Created: 02/Mar/21 09:38
• Updated: 09/Mar/21 07:53
• Resolved: 09/Mar/21 07:53

Description

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%.

Issue Links

• is duplicated by: NIFI-6518 Processors that are run on Primary Node Only should yield on all other nodes
• is related to: NIFI-6518 Processors that are run on Primary Node Only should yield on all other nodes
• is related to: NIFI-8300 Make non-source processors invalid if scheduled for Primary Node only