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
This issue is still open after a couple years (as of 9/2018). It looks like golang 1.9 does try to honor the cgroup memory limits but there's still a debate about what the application can do about handling OOM failures.
From the hive perspective of limiting container memory, this does look golang apps will be constrained but that services will need to specify how much to allocate to the heap and how much to allocate as buffer for other stuff, like stacks, etc.
Does GOLANG honor cgroup limits?
The text was updated successfully, but these errors were encountered: