How to configure the JVM, resource groups, and query to prevent worker restarts due to OutOfMemoryError (OOM)? #27446
Unanswered
A-little-bit-of-data
asked this question in
Q&A
Replies: 1 comment
-
|
@hashhar Sorry to bother you, but could you please help me out with my problem when you have some free time? I also consulted GPT and they suggested improvements to my configuration, such as adding |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
trino version : 430
The operating environment is Kubernetes.
resource group configuration
trino coordinator and worker deploy config

trino coordinator:
trino worker:
My current configuration is as shown above. I recently deployed some services, but I frequently encounter worker out-of-memory (OOM) errors, as shown in the following images.
Looking at the worker memory monitoring graph, the peak times are basically at 2 AM, 6 AM, 8 AM, and 8 PM, which are the peak business periods. We dare not reduce the concurrency any further at the moment. Are there any problems with the above configuration, or are there any areas that need to be optimized?
Beta Was this translation helpful? Give feedback.
All reactions