[
https://issues.apache.org/jira/browse/NIFI-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-9301.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> NiFi S2S connection causing it to be out of sync with NiFi registry.
> --------------------------------------------------------------------
>
> Key: NIFI-9301
> URL: https://issues.apache.org/jira/browse/NIFI-9301
> Project: Apache NiFi
> Issue Type: Bug
> Components: Flow Versioning
> Affects Versions: 1.14.0
> Environment: 2 x 5-node NiFi cluster
> 1 x NiFi regsitry
> Reporter: Leo Wang
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
