David, I would suggest giving a try with a recent build (even the binary of the failed 2.0 rc1 candidate* if you have no intent to build on your own) as there were quite a lot of changes around dependency management of python processors since m4, for eg this one: https://github.com/apache/nifi/pull/9429 , might fixing your issue.
*You can download the rc1 candidate binary from here: https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0/ Please let us know if it fixed the issue or you still face it, please share your nifi logs if there is something still wrong with this recent build! Thanks, regards, Arpad On Mon, Oct 28, 2024 at 6:51 PM David Gallagher < dgallag...@cleverdevices.com> wrote: > Hi - I've built a custom Python processor for the 2.0.0.M4 release. I'm > finding that I can't have two of the same processor running at the same > time (in different process groups). They seem to deadlock each other or > something. I'm not sure what to look at to see what's causing the problem. > Is this a known issue? I had a similar issue when trying to scale up the > python processor, I've only been able to get results if I keep it to 1 > thread. > > Thanks, > > Dave >
