You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We moved some of our workload from AWS EKS to Hetzner, courtesy of this Terraform module.
However our Java-based application experiences OOM conditions far more frequently than on AWS.
Heap is reported as MaxHeapSize = 92341796864 bytes. This is ~86 GB (92341796864 / 1024^3 ≈ 86 GB). So much of memory used by node itself (type is ccx53 in this case). This is not the case on EKS.
I know this might not exactly be Hetzner issue, or module issue, but I would like to know if someone else encountered similar issue and how they dealt with it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We moved some of our workload from AWS EKS to Hetzner, courtesy of this Terraform module.
However our Java-based application experiences OOM conditions far more frequently than on AWS.
Heap is reported as
MaxHeapSize = 92341796864
bytes. This is ~86 GB (92341796864 / 1024^3 ≈ 86 GB
). So much of memory used by node itself (type is ccx53 in this case). This is not the case on EKS.bash-4.2# cat /proc/meminfo | grep ^Mem MemTotal: 128792068 kB MemFree: 97818936 kB MemAvailable: 114766140 kB
we of course have resources set for our deployment, which - according to my knowledge - should constrain accessible resources for Pods:
I know this might not exactly be Hetzner issue, or module issue, but I would like to know if someone else encountered similar issue and how they dealt with it.
Here's OS:
Beta Was this translation helpful? Give feedback.
All reactions