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

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

[~bbende] 

regarding reproduce an issue:
 * using NiFi 1.23 (or any 1.xx) create flow containing JoltTransformJson 
processor
 * store flow to registry
 * using NiFi 2.0.0 cluster import flow from registry - both nodes in cluster 
will get/replicate the same flow with the same ghosted components
 * try to restart one of 2.0.0 nodes - it will fail to reconnect cluster 
regardless both flow have the same ghosted components and 2.0.0 nodes are 
identical with the same set of nar

So both nodes have SAME missing components but can not reconnect

> 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