Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Deleted NiFi workflow still running

Solved Go to solution
Highlighted

Deleted NiFi workflow still running

New Contributor

I have a NiFi deployment with five worker nodes. I launched a workflow that arised this error:

2018-11-22 16:58:06,368 ERROR [Timer-Driven Process Thread-2] o.a.n.processors.standard.ConvertRecord ConvertRecord[id=3ad5bd27-0167-1000-0000-0000256eb90d] Failed to process StandardFlowFileRecord[uuid=ef1f30cd-8d49-41e0-873f-5cfaf197a98d,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1542902286286-47374, container=default, section=270], offset=0, length=31760674],offset=0,name=yelp_business.csv.avro,size=31760674]; will route to failure: org.apache.nifi.processor.exception.ProcessException: org.apache.nifi.schema.access.SchemaNotFoundException: Unable to find schema with name 'inferred.avro.schema'org.apache.nifi.processor.exception.ProcessException: org.apache.nifi.schema.access.SchemaNotFoundException: Unable to find schema with name 'inferred.avro.schema'   at org.apache.nifi.processors.standard.AbstractRecordProcessor$1.process(AbstractRecordProcessor.java:132)   at org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:2827)   at org.apache.nifi.processors.standard.AbstractRecordProcessor.onTrigger(AbstractRecordProcessor.java:109)   at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)   at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1122)   at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:147)   at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)   at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:128)   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)   at java.lang.Thread.run(Thread.java:745)Caused by: org.apache.nifi.schema.access.SchemaNotFoundException: org.apache.nifi.schema.access.SchemaNotFoundException: Unable to find schema with name 'inferred.avro.schema'   at org.apache.nifi.schema.access.SchemaNamePropertyStrategy.getSchema(SchemaNamePropertyStrategy.java:60)   at org.apache.nifi.serialization.SchemaRegistryService.getSchema(SchemaRegistryService.java:117)   at org.apache.nifi.csv.CSVReader.createRecordReader(CSVReader.java:130)   at sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)   at java.lang.reflect.Method.invoke(Method.java:498)   at org.apache.nifi.controller.service.StandardControllerServiceInvocationHandler.invoke(StandardControllerServiceInvocationHandler.java:89)   at com.sun.proxy.$Proxy130.createRecordReader(Unknown Source)   at org.apache.nifi.processors.standard.AbstractRecordProcessor$1.process(AbstractRecordProcessor.java:113)   ... 14 common frames omittedCaused by: org.apache.nifi.schema.access.SchemaNotFoundException: Unable to find schema with name 'inferred.avro.schema'   at org.apache.nifi.schemaregistry.services.AvroSchemaRegistry.retrieveSchema(AvroSchemaRegistry.java:144)   at sun.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)   at java.lang.reflect.Method.invoke(Method.java:498)   at org.apache.nifi.controller.service.StandardControllerServiceInvocationHandler.invoke(StandardControllerServiceInvocationHandler.java:89)   at com.sun.proxy.$Proxy131.retrieveSchema(Unknown Source)   at org.apache.nifi.schema.access.SchemaNamePropertyStrategy.getSchema(SchemaNamePropertyStrategy.java:53)   ... 22 common frames omitted

I stopped the workflow, deleted it and restarted NiFi several times, but some of the workers continue showing this error.

Thank you.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Deleted NiFi workflow still running

Master Guru

@Mikel Emaldi

-

The particular error points at a very specific processor still on the canvas that is trying to process a FlowFile.

Search your canvas for the component uuid in the error log message. In above error that uuid is 3ad5bd27-0167-1000-0000-0000256eb90d

-

NiFi will not allow you to delete a connection that still contains FlowFiles. So the particular dataflow that you have deleted was not the dataflow containing this particular processor because it would have had an inbound connection with this FlowFile still present on it.

-

Thank you,

Matt

-

If you found this answer addressed your question, please take a moment to login in and click the "ACCEPT" link.

2 REPLIES 2

Re: Deleted NiFi workflow still running

Master Guru

@Mikel Emaldi

-

The particular error points at a very specific processor still on the canvas that is trying to process a FlowFile.

Search your canvas for the component uuid in the error log message. In above error that uuid is 3ad5bd27-0167-1000-0000-0000256eb90d

-

NiFi will not allow you to delete a connection that still contains FlowFiles. So the particular dataflow that you have deleted was not the dataflow containing this particular processor because it would have had an inbound connection with this FlowFile still present on it.

-

Thank you,

Matt

-

If you found this answer addressed your question, please take a moment to login in and click the "ACCEPT" link.

Re: Deleted NiFi workflow still running

New Contributor

Hi @Matt Clarke, thank you for your response.

The problem was that, for any reason, nifi nodes were not synchronized and each of them was running a different workflow. I have copied the correct flow.xml.gz to all nodes and everything works fine now.

Regards.