@Gubbi  What that stat is telling you is that the processor executed a total of 297 threads in the past 5 minutes.  You can see that the cumulative time for all 297 threads that executed was only 0.044 seconds.  So we can see that these 297 threads consumed in total very little time on the CPU.  What this also tells us is that the processor executed about every 1 sec.   This is either because your configured run schedule is every 1 sec (0 sec is default) or there where no new files found when it did each execution.  To prevent a processor from consuming excessive CPU when the run schedule is set to 0 sec, NiFi will yield a processor after a thread runs which produces no results.   What you have shown looks to be as expected behavior. Thanks, Matt ... View more

@Gubbi    Not sure what you mean by spikes up to 300. A screenshot(s) maybe helpful to understand what you are observing. ... View more

@Gubbi    It is impossible to say what is going on here without more detail. From where are you determining NiFi is using  greater than 100% CPU? If you are you are looking at top, with 8 cpu you would have 800% cpu available (100% for each of the 8 cpu).   So 100%+ my be normal expected for the NiFi Java process.  You have the NiFi core process running, plus each processor can execute concurrently.  For example, FetchFile may be fetching the content of FLowFile 2 while PutS3 is putting FlowFile 1 to S3 at the same time.  Since NiFi is designed to multi threaded, it is possible that multiple threads being executed concurrently, with each of those threads being handled by a different CPU.  By default, the configured "Max Timer Driven Thread Count" in NiFi is set to 10.  This means that across all processors 10 threads can be requested concurrently.  This is a soft limit, so there are scenarios where the number of active threads can extend beyond the max configured thread count. Plus core level thread are used which do not come from this thread pool which is used only by NiFi components added to the canvas. What other processes are consuming CPU on your system? How is your NiFi configured, what are all the processors on your canvas, how are they configured, how large are the 3 files you are processing, what do the tasks/time stats on your processors show when this dataflow is executing against your 3 FlowFiles, etc? Hope this helps give you some direction to investigate. Matt ... View more

@saivenkatg55    You need to literally use ./keystore.p12 in your command instead of just keystore.p12 curl --cert-type P12 --cert ./keystore.p12:password --cacert nifi-cert.pem -v https://w0lxqhdp04:9091/nifi-api/flow/search-results?q=     Hope this helps, Matt ... View more

@vineet_harkut    I recommend starting a new question since this one already has a resolution.  You'll get better responses that way.   But the clientId can be whatever you want to use.  For example even below would work: "revision":{"clientId":"1","version":0} The JSON response will have the UUID for the component you created which you would then use to modify the configuration of that component in future rest api calls.   Thank you, Matt ... View more

@justjoe    With Apache NiFi 1.0 - 1.9 versions, only input and output ports added at the root canvas level (very top level) will be "remote" input/output ports.  All input/output ports added within sub-process groups are local ports only.  NiFi Remote Process Groups (RPG) are only able to send to or pull from "remote" input and output ports. With Apache NiFi 1.10 and newer you can now have the option of designating an input or output port as either local or remote when it is being added to the canvas within a sub process group.   Hope this helps, Matt ... View more

@nishank_paras    First we need to asks questions to better understand the http cloud endpoint: How do you currently accomplish this task outside of NiFi? Is it possible to connect via a terminal/command prompt to get the file from the http cloud server? Does the http cloud service have a rest-api for getting data from it?   My first thought would be the invokeHTTP processor to get your file from the http cloud server... Then use an UpdateAttribute processor to change the "filename" attribute value on the NiFi FlowFile created by the invokeHTTTP processor...  You did not mention what you want to do with this file once you have retrieved it ad renamed it in NiFi.  Are you trying to write it back to the same http cloud service?  Are you trying to write the file to another service/endpoint?  Are you writing it to a local directory?   Then we can start to look at what processors NiFi may have available to accomplish the same methods.   Hope this helps get you started, Matt ... View more