Closed kiritowu closed 2 years ago
Hey, @kiritowu.
What is the expected behavior here? Of course, if the Executors are not yet started, sending a query when they are not ready will not fail? Would you expect a better error handling or what exactly?
@JoanFM In Jina 2.x, when the executors are starting, the behaviour which I experienced is that any request will be put on hold until all the executors are ready to process the request.
The reason why this bug is slightly inconvenient is that when I deployed this as a container on the cloud, the container would only be started when a new request is sent. However, since the container is just spinning up and all the executors are in the preparing phase, the error ended up being propagated to the HTTP client.
What I am looking for is a similar behaviour in Jina 2.x whereby the content of the request is sent to the executors only when all executors are ready. Hope that better clarifies.
Hey @kiritowu,
Due to the changes of 3.0 this behavior is by nature not there.
What you need to do is to make sure that the Executors are ready.
This can be done in 2 ways;
Describe the bug An error will arise when a new request is being sent while waiting for all executors to be ready.
MWU to reproduce (Slightly modified from the previous issue):
Error Message: (Ignore the ContentTypeError but the real problem is the ERROR: Exception in ASGI application portion)
Environment