[action] [PR:11738] Memory exhaustion test case takes an indeterminate amount of time to trigger Kernel panic.#12105
Merged
mssonicbld merged 1 commit intosonic-net:202311from Mar 22, 2024
Conversation
…trigger Kernel panic. (sonic-net#11738) * Turned swapping off so kernel catches OOM in a shorter time.
Merged
7 tasks
Collaborator
Author
|
Original PR: #11738 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Fixes # 11737
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
It seems the time it takes for the kernel to raise Out of Memory condition and trigger oom_killer is not very deterministic in this test case. Once memory is exhausted in the system, the node becomes very unresponsive as no new processes can be created. Under most cases the test does complete in 10 mts, however for some of the PIDs, the test takes 20, 30 mts or more.
It seems the issue is seen in Linux operation in other scenarios - https://unix.stackexchange.com/questions/373312/oom-killer-doesnt-work-properly-leads-to-a-frozen-os
The solution seems to be to disable the swapping so the kernel raises the OOM condition much faster.
https://askubuntu.com/questions/1188024/how-to-test-oom-killer-from-command-line
How did you verify/test it?
Ran the test case on a number of PIDs.