Isha, If you have an incoming connection, and you’re seeing this, then it’s a bug. If there is no incoming connection and this processor is used as a source processor, it’s normal. Either way, it has rather little overhead, and you can further reduce the overhead by increasing the Yield Duration in settings. This is how long it will wait between invocations if there’s nothing for it to do.
Either way, best to file a Jira, though, to address the behavior for running unnecessarily when there’s an incoming Connection. Thanks -Mark > On Jun 12, 2023, at 8:36 AM, Isha Lamboo <isha.lam...@virtualsciences.nl> > wrote: > > Hi all, > > I have a question about behavior I see on one of our NiFi 1.18 clusters that > has a lot of xHDFS processors. When I look at the number of tasks in the > summary, the DeleteHDFS processors have a very high number (800-1000+) of > tasks even if they have nothing in their incoming queues. The PutHDFS and > FetchHDFS in contrast have no tasks listed when they have no files in the > incoming queues. Even though the tasks take very little time (less than 100 > millis per 5 mins), I’m wondering whether this causes problems when the > cluster is heavily loaded during peak hours. > > Is this a bug or some feature related to deleting files? Should I submit a > ticket? > > Thanks, > > Isha
