Local Container bento (works) <-> Yatai build Bento (fails with async issue) about yatai HOT 5 CLOSED

Hi @rishin27 - BentoML internally uses async everywhere for better performance, so this might be an internal issue with BentoML on Yatai, that's not related to user code. May I ask what's the BentoML and Yatai version that you are using?

Note that when a Bento is deployed on Yatai, Runners are by default scheduled as their own separate pods, in order to scale separately from the service code. The async code path is used for converting the runner.run function call into an async RPC call. This might be an issue with how the deployment and runner communication was set up.

from yatai.

Hi @parano Thanks for the info. I get that yatai is build for autoscaling & kubernetes workload magic. But if the user has nowhere marked their code as async, is it right to send it by default to the async code path ?
The general workflow for a data scientist will be that they'll build the model, save it using bento, check if the service is working using 'bentoml serve'... if everything works out will push it to the yatai server for the deployment. But then if yatai adds async magic (which was not intended) and thing start breaking, it'll not be a good UX.

Yatai - v0.3.1-c3dab74
bentoml - v1.0.0a7

from yatai.

Thanks @rishin27, we will look into this issue more. Ideally by design, if the bentoml serve works locally, it should definitely work on Yatai. Note that Yatai is still in its alpha release so definitely expect some rough edges at the moment.

But if the user has nowhere marked their code as async, is it right to send it by default to the async code path ?

This is actually fairly common in python web frameworks, such as Sanic or FastAPI, where both sync and async handlers can be defined by the user, the framework uses async internally. BentoML server uses async even without Yatai. I think the root cause of the issue is likely not about async, but some settings with the distributed runner setup in yatai deployment.

from yatai.

Thanks @parano for your detailed answer.
Do let me know if i can help, happy to contribute.

from yatai.

Hi @rishin27, could you try it again with the latest version of BentoML and Yatai? The issue should be resolved by now.

from yatai.