Support Questions

Find answers, ask questions, and share your expertise

NiFi node cannot connect cluster for a flow version is delete from registry

New Contributor

After deleteing all version of a flow from nifi registry, restarting a node cannot connect cluster, It always display below error. How can I resolve it?

 

2021-12-16 22:13:17,520 ERROR [Timer-Driven Process Thread-149] o.a.nifi.groups.StandardProcessGroup Failed to synchronize StandardProcessGroup[identifier=d059cc81-0176-1000-0000-0000089d93e4,name=整机CMES] with Flow Registry because could not retrieve version 3 of flow with identifier 5d63465f-9893-4f93-8d27-b8c258519d68 in bucket fbcc346b-ee7c-4ec4-ba7d-68c0f4c306b1
org.apache.nifi.registry.client.NiFiRegistryException: Error retrieving flow snapshot: The specified flow ID does not exist in this bucket.
        at org.apache.nifi.registry.client.impl.AbstractJerseyClient.executeAction(AbstractJerseyClient.java:117)
        at org.apache.nifi.registry.client.impl.JerseyFlowSnapshotClient.get(JerseyFlowSnapshotClient.java:97)
        at org.apache.nifi.registry.flow.RestBasedFlowRegistry.getFlowContents(RestBasedFlowRegistry.java:213)
        at org.apache.nifi.registry.flow.RestBasedFlowRegistry.getFlowContents(RestBasedFlowRegistry.java:227)
        at org.apache.nifi.groups.StandardProcessGroup.synchronizeWithFlowRegistry(StandardProcessGroup.java:3761)
        at org.apache.nifi.controller.FlowController$6.run(FlowController.java:972)
        at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found
        at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:916)
        at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:723)
        at org.glassfish.jersey.client.JerseyInvocation.lambda$invoke$1(JerseyInvocation.java:643)
        at org.glassfish.jersey.client.JerseyInvocation.call(JerseyInvocation.java:665)
        at org.glassfish.jersey.client.JerseyInvocation.lambda$runInScope$3(JerseyInvocation.java:659)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:205)
        at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:390)
        at org.glassfish.jersey.client.JerseyInvocation.runInScope(JerseyInvocation.java:659)
        at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:642)
        at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:417)
        at org.glassfish.jersey.client.JerseyInvocation$Builder.get(JerseyInvocation.java:313)
        at org.apache.nifi.registry.client.impl.JerseyFlowSnapshotClient.lambda$get$1(JerseyFlowSnapshotClient.java:104)
        at org.apache.nifi.registry.client.impl.AbstractJerseyClient.executeAction(AbstractJerseyClient.java:103)
        ... 12 common frames omitted

 

 

1 ACCEPTED SOLUTION

New Contributor

I have fixed the issue by removing registry label about the flow from flow.xml.gz. Then node can start to connect cluster.

View solution in original post

1 REPLY 1

New Contributor

I have fixed the issue by removing registry label about the flow from flow.xml.gz. Then node can start to connect cluster.

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.