Description
When you first add a python processor to canvas / restart nifi, for the releated python processor a Controller.py processor is start, which handle communication between python / java, etc..
If you kill this processor (simulate an error in it, or some other reason the processor die), nifi is not restart it and eventually processor became invalid:
When this happens, the only solution is to restart nifi.
This is not good for production use cases (imagine if you realize this error 1 week later) so we need to extend pythonBridge logic to:
- periodically check status of the started process
- If process is not running, try to restart it and log the problem into nifi log
Attachments
Attachments
Issue Links
- fixes
-
NIFI-11446 Better handling for cases where Python process dies
-
- Resolved
-
- links to
