[NIFI-9301] NiFi S2S connection causing it to be out of sync with NiFi registry.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.14.0
• Component/s: Flow Versioning
• Environment: 2 x 5-node NiFi cluster ; 1 x NiFi regsitry
• Assignee: Unassigned
• Reporter: Leo Wang
• Created: 13/Oct/21 21:53
• Updated: 13/Oct/21 21:53

Description

We have 2 separate 5 node NiFi clusters that shares the same flows across the two clusters. One of the flow contains a S2S remote process group, with multiple connections. When we make a change to the flow and commit the change to registry on the 1st cluster and update on the 2nd cluster; the 2nd cluster's update will automatically introduce a local change regarding to the source/connection, stating it is different even though it is the same on the other cluster. The automatic local change causes the flows on the 2 clusters to be out of sync with one another. When we repeat the process the same thing happens on the other cluster, where one is in sync and one is not.

The current work around we are doing is layering it by putting the S2S remote process group inside another processor group and have the connections connect to local input and outputs.