[ 
https://issues.apache.org/jira/browse/NIFI-13613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870939#comment-17870939
 ] 

Night Gryphon commented on NIFI-13613:
--------------------------------------

[~bbende] yep. The log message is exactly the same as in the test. BUT in this 
case the flow was imported and everything was fine except for that part of flow 
containing missing components. User was able to manually fix that part of 
imported/migrated flow. Until  one node was restarted.

"Proposed flow has missing components that are not considered missing in the 
current flow". BUT at the running node this component is also mising so it 
should be ok to join...
{code:java}
Caused by: org.apache.nifi.controller.UninheritableFlowException: Proposed Flow 
is not inheritable by the flow controller because of differences in missing 
components: Proposed flow has missing components that are not considered 
missing in the current flow 
(ff645cee-203b-3805-8d03-4a6c3b5518df,ff645cee-203b-3805-ae7c-8eeae6145bdd,ff645cee-203b-3805-a2a6-5e07e9bb31c2,ff645cee-203b-3805-af69-868ee03bf110)
    at 
org.apache.nifi.controller.serialization.VersionedFlowSynchronizer.sync(VersionedFlowSynchronizer.java:180)
    at 
org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1743)
    at 
org.apache.nifi.persistence.StandardFlowConfigurationDAO.load(StandardFlowConfigurationDAO.java:91)
    at 
org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:805)
    at 
org.apache.nifi.controller.StandardFlowService.loadFromConnectionResponse(StandardFlowService.java:954)
    ... 5 common frames omitted
2024-08-01 10:28:32,843 INFO [main] o.a.n.c.c.node.NodeClusterCoordinator 
nifi2.nifi.local:8443 requested disconnection from cluster due to 
org.apache.nifi.controller.UninheritableFlowException: Failed to connect node 
to cluster
2024-08-01 10:28:32,847 ERROR [main] o.a.n.c.c.node.NodeClusterCoordinator 
Event Reported for nifi2.nifi.local:8443 -- Node disconnected from cluster due 
to org.apache.nifi.controller.UninheritableFlowException: Failed to connect 
node to cluster
2024-08-01 10:28:32,847 INFO [main] o.a.n.f.c.l.z.CuratorLeaderElectionManager 
Cannot unregister Leader Election Role 'Primary Node' because that role is not 
registered
2024-08-01 10:28:32,847 INFO [main] o.a.n.f.c.l.z.CuratorLeaderElectionManager 
Election Listener for Role Cluster Coordinator disabled
2024-08-01 10:28:32,847 INFO [main] o.a.n.f.c.l.z.CuratorLeaderElectionManager 
Unregistered for Election: Role [Cluster Coordinator]
2024-08-01 10:28:32,848 INFO [main] o.a.n.c.c.node.NodeClusterCoordinator Node 
ID [nifi2.nifi.local:8443] Disconnection Code [Node was Shutdown] send completed
2024-08-01 10:28:32,848 INFO [main] o.apache.nifi.controller.FlowController 
Initiating shutdown of FlowController...{code}
 

> 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)

Reply via email to