How to bring my windows AKS windows node back to sanity (memory wise) after having run a very RAM intensive workload? #5070
Unanswered
MarkKharitonov
asked this question in
Q&A
Replies: 0 comments
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.
-
I have an AKS windows node pool. Here is its host memory breakdown before running the heavy RAM intensive workload for over 4 hours:
Here it is 25 hours after the heavy workload finished:
The extra 2GB of the total process memory is not a concern (the heavy container is idle, but still takes up memory)
What is a concern is that the kernel memory is not released. And I have no idea how to deal with it except restart the node.
Are there any other options here?
Beta Was this translation helpful? Give feedback.
All reactions