Skip to content
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

Is there any way not to kill container when exceed memory limit,but to stop the process inside the container? #82516

Open
toyow opened this issue Sep 10, 2019 · 4 comments

Comments

@toyow
Copy link

commented Sep 10, 2019

when ommkill happened,the third party librar installed by user can‘t be recovered。Is there any way to solve this problem?
community/question

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

commented Sep 10, 2019

@toyow: There are no sig labels on this issue. Please add a sig label by either:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <group-name>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals.

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.

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

commented Sep 10, 2019

@toyow: The label(s) sig/oomkill cannot be appled. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other

In response to this:

when ommkill happened,the third party librar installed by user can‘t be recovered。Is there any way to solve this problem?
/sig oomkill

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.

@tossmilestone

This comment has been minimized.

Copy link
Contributor

commented Sep 10, 2019

@toyow The behavior of OOMKill is killing the container process, not the Pod. And that's exactly what you desire.

@toyow toyow changed the title Is there any way not to kill pod when exceed memory limit,but to stop the process inside the container? Is there any way not to kill container when exceed memory limit,but to stop the process inside the container? Sep 10, 2019

@toyow

This comment has been minimized.

Copy link
Author

commented Sep 10, 2019

@toyow The behavior of OOMKill is killing the container process, not the Pod. And that's exactly what you desire.

Thank you for your reminder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.