Out of Memory Error on Trino Pod Despite Memory Limits Configured #24196
Replies: 1 comment 2 replies
-
Resource groups only perform admission control. The config you have doesn't mean queries will fail if they use more than 46GB of memory, it means that newly submitted queries will have to wait until memory consumption falls below 46GB. To limit memory usage see max-memory-per-node and max-memory from https://trino.io/docs/current/admin/properties-resource-management.html#query-max-memory-per-node |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello Trino Community,
I am encountering an Out of Memory (OOM) error with my Trino deployment on Azure Kubernetes Service (AKS). Despite configuring several memory limits, my pod was restarted because it breached the total node memory limit of 62 GiB. Here’s the setup I have:
AKS Node Memory: 62 GiB
Pod Memory Limits:
CPU Limit: 7000m
Memory Limit: 58.5 GiB
Soft Memory Limit: 46 GiB configured in the resource group.
Query Max Memory: 18 GiB
Configuration Files
resource-group.json:
jvm.config:
Issue:
Despite these configurations, the pod still encountered an OOM error and was restarted after breaching the 62 GiB node limit.
Questions:
Could you help me understand why the pod would breach the 62 GiB limit even with the defined soft and hard memory limits?
Are there any additional configurations or best practices I should consider to prevent this issue in the future?
Thank you for your assistance!
Beta Was this translation helpful? Give feedback.
All reactions