[NIFI-4905] If cluster response time is slow - there isn't enough information to help the operator know why

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.5.0
• Component/s: Core UI
• Environment: Centos 7.3 ; NiFi 1.5.0 Cluster with 8 physical nodes
• Assignee: Unassigned
• Reporter: Josef Zahner
• Created: 23/Feb/18 13:31
• Updated: 23/Feb/18 16:37

Description

we are actually working on a PoC with 8 nodes (HP BL460c Blades, 24 Cores, 44GB RAM) in a NiFi 1.5.0 cluster. Our configuration has about 160 processors and all of them are stopped. Even in the stopped state, we are constantly getting the messages below for all nodes, not only for the primary node.

Response time from nifi2-07.xyz.ch:8080 was slow for each of the last 3 requests made. To see more information about timing, enable DEBUG logging for org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator

If you are on the root canvas, you feel that it takes a few seconds until it response after a refresh. We have already tuned the parameters below, but without any luck. After restart of NiFi it is fine for a few minutes, but then the messages return.

nifi.cluster.protocol.heartbeat.interval=15 sec
nifi.cluster.node.protocol.threads=40
nifi.cluster.node.protocol.max.threads=80
nifi.cluster.node.connection.timeout=60 sec
nifi.cluster.node.read.timeout=60 sec

The nodes have absolutely no load beside of NiFi. What surprised me was, that when the UI refreshs (default every 30s) it produces about 20% cpu load on my machine. And remember, it's a 24x2.9GHz blade server.

That's a picture of my root canvas:

Actually we can't work with the cluster under this circumstances because the gui always gets so slow.

Is this a bug or normal behavior? Do we have to many elements on the GUI or what could cause this issue?

Cheers