Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python warmupTrigger doesn't run on all workers on a scaled-out instance, and requests are sent to worker processes that aren't warm yet #2462

Open
empowerNate opened this issue Mar 26, 2024 · 0 comments
Labels

Comments

@empowerNate
Copy link

I found this happening on the Elastic Premium plan but assume the same problem happens on the Dedicated plan. I implemented a warmupTrigger with the V2 programming model, and it works on some of the worker processes within a scaled-out instance. However, it doesn't get called on all the workers, and some requests are sent to workers before they are fully warmed up. On an EP3 instance, it only got called on 2 of 4 workers, for example.

Additionally, I tried adding a long time.sleep to the warmupFunction of 10 * n_workers. However, the same worker where the warmupTrigger runs will start receiving requests before the warmupTrigger has finished, weirdly. I was hoping this could be a hack to make the warmupTrigger work despite the bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant