Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Not A Problem
-
1.9.1, 1.9.2
-
None
-
None
-
Linux
-
Important
Description
In a containerized environment, When a NiFi node doesn't meet health probes performed by Kubelet (Kubernetes), then the node is killed and restarted. This may loop continuously causing NiFi Cluster page ( Hamburger Menu -> Cluster ) to show multiple entries for the same node that gets restarted again and again.
To replicate the issue:
1. Setup single-node cluster ( statefulset application with replicaCount = 1)
2. Change configured probes such as Startup or Liveness to duration less than regular node start up time .
3. Scale new node (replicaCount), for example from 1 to 2. Then new scaled node node-1 gets killed and restarted continuously by kubelet .
Please check the screenshot below.
nifi-1:8080 is being added 7 times when it should be added just once, This shows incorrect 1/8 nodes cluster summary when expected behavior is just 1/2 nodes .