-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fix OOM virtiofs container limit #9228
Conversation
Signed-off-by: Romà Llorens <roma.llorens@gmail.com>
Hi @rumans. Thanks for your PR. I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
/approve
/ok-to-test
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jean-edouard The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
/retest-required |
/retest-required |
3 similar comments
/retest-required |
/retest-required |
/retest-required |
@rumans: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest-required |
Signed-off-by: Romà Llorens roma.llorens@gmail.com
What this PR does / why we need it:
We found that with intensive disk usage, virtiofs container OOMs at the current limit (40M)
Bumping this limit to 80M solved our issue (Max usage observed is 71M)
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Issue discussed on Slack Channel with @xpivarc
Release note: