@bowen, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future. ... View more

Hi @MrBeasr  Please check the status of job via Oozie Database: # select count(*) from WF_JOBS where id like '%0043858-220322202819429-oozie-oozi-W%';   If require you may set the status of the job in Database itself: # update wf_jobs set status='FAILED' where id like '%0043858-220322202819429-oozie-oozi-W%';  ... View more

Congratulations ... View more

@Choolake, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future.  ... View more

I suspect one more NiFi service is running on the same host with the same port, It can be checked easily by running "ps -ef | grep nifi"   ... View more

@shofialau Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future.  ... View more

@broobalaji  HDF 1.8.0.3.3.1.0-10 was released way back in 2017.  I strongly recommend upgrading to a much newer release of CFM.   NiFi Templates have been deprecated and are completely removed as of Apache NiFi 2.x releases.  Apache NiFi deprecated templates for a number of reasons: 1. Templates uploaded to NiFi (even if not instantiated/imported to the NiFi canvas reside within NiFi's heap memory space)  2. Large uploaded templates or many uploaded templates can have a substantial impact on NiFi performance because of the amount of heap they can consume.  Simply increasing the size of NiFi's heap is also not the best solution to that heap usage as large heaps just lend themselves to longer stop-the-world garbage collections with the JVM.  3. Apache NiFi deprecated and moved away from using xml based flow in favor of json flow definitions around the Apache NiFi 1.16 time frame.   Flow definitions (JSON files) can exported and imported without uploading them in to heap memory within NiFi. The above info aside.... It is best to use the developer tools available in your web browser to inspect/capture the rest-api call being made when you perform the same steps directly via the NiFi UI.  This makes it easy to understand the calls that need to be made in your automation.  I also encourage you if you continue to use templates to upload, import to UI, and then delete the uploaded template to minimize heap impact. Thanks, Matt ... View more