[
https://issues.apache.org/jira/browse/NIFI-13613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871253#comment-17871253
]
Night Gryphon commented on NIFI-13613:
--------------------------------------
[~bbende] looks like that. Should we rename or create separate ticket to
investigate and fix this behavior?
I also found some not clear behavior while trying to restore cluster.
To restore cluster using web ui i've deleted disconnected node from cluster
which allowed me to delete the process group containing ghosted components.
Than i've tried to restart failed node as is and the just deleted process group
magically _reappear_ with all the ghosted components and that node failed
again.
So to restore the cluster i has to delete node again than delete process group
than delete flow.json.gz from failed node and finally restart failed node. That
did the trick and cluter was restored.
> 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)
