-
Notifications
You must be signed in to change notification settings - Fork 7
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
Trino workers autoscaling #12
Comments
Hi @adwiza, I personally would argue it's the responsibility of the Trino cluster itself to scale the number of workers based on e.g. number of running/queued queries, CPU or some other metric. But I'm also happy about feedback, if you have different opinions. E.g. at Stackable we will probably utilize Horizontal Pod Autoscaling for that, created stackabletech/trino-operator#532 for that The community helm-chart of Trino uses the mentioned approach once you enable |
Hi @sbernauer I haven't mentioned, but that we are using the Trino operator and I guess this solution doesn't fit for us, does it? |
Sorry, did I get it correctly that you are using https://github.com/stackabletech/trino-operator? In this case you sadly need to wait for stackabletech/trino-operator#532 to have auto-scaling for the workers. |
Yes it is, we are using the https://github.com/stackabletech/trino-operator |
Hi @adwiza https://docs.stackable.tech/home/stable/concepts/operations/#_performance |
@soenkeliebau it works, thank you, I've added the HPA configuration with needed behavior that's all |
That is great to hear, thank you for reporting back! |
Closing in favour of stackabletech/trino-operator#532 |
Hi, we need to scale up and down the Trino workers in Trino cluster, can we use this to to solve this issue, or we need to use an alternative approach, could you please cheet to us how to deal with Trino workers autoscaling?
The text was updated successfully, but these errors were encountered: