[
https://issues.apache.org/jira/browse/NIFI-13613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870733#comment-17870733
]
Bryan Bende commented on NIFI-13613:
------------------------------------
I think we need more information about how to reproduce the problem where the
node can't connect.
I did the following:
* Started 2 node cluster using latest main (2.0.0-M4 + more)
* Add JoltTransformJson processor
* Stopped both nodes
* Remove the nifi-jolt-nar from lib dir of both nodes
* Started nodes back up and component is ghosted
* Stopped node 2 and started it again, joined cluster again
* Also performed a disconnect of node 2 in UI, then a Connect, and it
connected back
A variation of this test is:
* Started 2 node cluster using latest main (2.0.0-M4 + more)
* Add JoltTransformJson processor
* Stopped node 2
* Removed nifi-jolt-nar from node 2
* Start node 2 again, get the following exception:
{code:java}
Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed Flow
is not inheritable by the flow controller because of differences in missing
components: Current flow has missing components that are not considered missing
in the proposed flow (18ca2c01-0191-1000-ffff-ffffd6e7283e)
at
org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.sync(VersionedFlowSynchronizer.java:186)
at
org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1800)
at
org.apache.nifi.persistence.StandardFlowConfigurationDAO.load(StandardFlowConfigurationDAO.java:91)
at
org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:817)
at
org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:969)
... 5 common frames omitted {code}
This is correct behavior because the processor was not ghosted on node 1.
> Update class names when import older flow from registry
> -------------------------------------------------------
>
> Key: NIFI-13613
> URL: https://issues.apache.org/jira/browse/NIFI-13613
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.0.0-M3
> Environment: Ubuntu 22.04
> Open JDK 21
> NiFi Registry 2.0.0.M3
> Reporter: Night Gryphon
> Priority: Critical
>
> I'm trying to migrate from NiFi 1.23 to 2.0.0 using NiFi Registry.
> When i import flow to 2.0.0 i get some missing components due to package
> names changes for some components like JOLT.
> The issue/bug is having such flow prevent cluster nodes to restart/rejoin.
> Once node is shutdown or disconnected from cluster it can't come back as it
> can't sync flow with master node due to missing components and so node just
> shutdown. Furthermore at the master node i can not delete or fix the corrupt
> process group as some nodes are unavailable and can't rejoin cluster.
> So to recover i has to delete nodes from cluster, delete process group and
> than rebuild cluster.
> To fix this issue class names has to be checked at the flow import and
> replaced according to updates in 2.0.0.
> Also flow sync at join cluster has to somehow deal with missing components
> which are exist in master flow and actually can be displayed and manually
> fixed.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
