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

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

[~bbende] i didn't make rolling upgrade. i'm trying to migrate to completely 
new just installed cluster using registry to transfer flows from old cluster to 
brand new one. So both nodes are the same 2.0.0-M3. At the moment node 
disconnects all the nodes was synchronized and have identical flow which 
contain ghosted components. And after disconnect a node it can't connect back 
having exactly the same flow as the cluster.

> 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