WojciechWitos created NIFI-15342:
------------------------------------
Summary: Node's Flow did not Match Cluster Flow
Key: NIFI-15342
URL: https://issues.apache.org/jira/browse/NIFI-15342
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 2.7.1, 2.7.0
Environment: NiFi Clustered version.
3 nodes = 4 CPU, 20 GB RAM, RHEL 9
Reporter: WojciechWitos
Hi!
During standard upgrade of NiFi from version 2.6 to 2.7.0 and later on 2.7.1
we've faced an issue with cluster - using embeded zookeeper.
After turning on NiFi cluster couldn't synchronize due to the differences in
the flow.
Flow.json.gz has been removed from 2 hosts (3 in the cluster).
Also flow couldn't be synchronized. The only error which we get in the
nifi-app.log is:
{code:java}
2025-12-15 09:48:41,645 INFO [Process Cluster Protocol Request-45]
o.a.n.c.c.node.NodeClusterCoordinator Status of XXXXX:8443 changed from
NodeConnectionStatus[nodeId=XXXXXX:8443, state=DISCONNECTED, Disconnect
Code=Node's Flow did not Match Cluster Flow, Disconnect
Reason=org.apache.nifi.controller.serialization.FlowSynchronizationException:
Failed to connect node to cluster because local flow controller partially
updated. Administrator should disconnect node and review flow for corruption.,
updateId=44] to NodeConnectionStatus[nodeId=XXXXX:8443, state=DISCONNECTED,
Disconnect Code=Node's Flow did not Match Cluster Flow, Disconnect
Reason=org.apache.nifi.controller.serialization.FlowSynchronizationException:
Failed to connect node to cluster because local flow controller partially
updated. Administrator should disconnect node and review flow for corruption.,
updateId=44] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
