-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloudhealth-collector pod gets restarted due to emptydir #119
Conversation
Currently there’s no limit for the amount of memory the emptydir can consume, according to kubernetes/kubernetes#119611 this may end up crashing the node as the memory limit is not being considered when using emptydir (the emptydir can consume all the memory of the node, resulting in other processes being killed). Setting the limit to half of the allocated memory should be fine.
@bbilali, we have received your signed contributor license agreement. The review is usually completed within a week, but may take longer under certain circumstances. Another comment will be added to the pull request to notify you when the merge can proceed. |
Thank you for your contribution! Our team will take a look in the next few days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good one! we never reached the scenario where this tmpfs becomes large by any standard. And all our Nodes are disk backed instead of memory..
Glad we have a fix this scenario! Thank you!
Thank you for your patience! We are in contact with the Open Source team regarding your contributor license agreement and will get back to you once it is reviewed |
@bbilali, VMware has approved your signed contributor license agreement. |
Currently there’s no limit for the amount of memory the emptydir can consume, according to kubernetes/kubernetes#119611 this may end up crashing the node as the memory limit is not being considered when using emptydir (the emptydir can consume all the memory of the node, resulting in other processes being killed). Setting the limit to half of the allocated memory should be fine.