Worker killed by ping-pong health check when calling C/Java code via Python interface #2677
-
After upgrading to uvicorn 0.30.0 from 0.29.0, my API endpoint that calls a Python interface to a C library (which in turn calls Java code) fails to work. The worker porcess is killed due to the new ping-pong health check mechanism. This setup works fin in Uvicorn 0.29.0 where the ping-pong check is not present. If I hack the library and retur True always for is_alive method of uvicorn.supervisors.multiprocess.Process.is_alive the entire setup works again => ping-pong mechanism is not working. All version of uvicorn starting from 0.30.0 and above, I'm facing this issue If I hack the is_alive(timeout=5) to higher timeout values it works. I hope if there can be some setting in future versions to modify this timeout. Python version: 3.11.9 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I'm going to merge this: #2711. |
Beta Was this translation helpful? Give feedback.
I'm going to merge this: #2711.