-
Notifications
You must be signed in to change notification settings - Fork 3
chore(core): workaround for oomkills during imports #1573
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
chore(core): workaround for oomkills during imports #1573
Conversation
Temporarily increase memory limit value to workaround OOMKill during importing huge images ~2.9GiB on linux kernels 6.12+. Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
Reviewer's guide (collapsed on small PRs)Reviewer's GuideTemporarily raised the memory limit for the importer container in the CDI configuration to 3600M to prevent OOMKills when handling large (~2.9GiB) image imports on newer Linux kernels, with a TODO to revert once the root cause is addressed. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
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.
|
Success on new cluster with nodes on linux kernel 6.12+. |
Temporarily increase memory limit value to workaround OOMKill during importing huge images ~2.9GiB on linux kernels 6.12+. Port #1573 to upstream. Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
Temporarily increase memory limit value to workaround OOMKill during importing huge images ~2.9GiB on linux kernels 6.12+. Port #1573 to upstream. Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
Description
Temporarily increase memory limit value to workaround OOMKill during importing huge images ~2.9GiB on linux kernels 6.12+.
Why do we need it, and what problem does it solve?
What is the expected result?
Checklist
Changelog entries