DRT: Added DRT operation for OOM kill#169406
Open
cpj2195 wants to merge 1 commit intocockroachdb:masterfrom
Open
DRT: Added DRT operation for OOM kill#169406cpj2195 wants to merge 1 commit intocockroachdb:masterfrom
cpj2195 wants to merge 1 commit intocockroachdb:masterfrom
Conversation
Contributor
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
Member
f36e286 to
305c2a0
Compare
305c2a0 to
e9ebbf2
Compare
|
Detected infrastructure failure (matched: self-hosted runner lost communication with the server). Automatically rerunning failed jobs. (run link) |
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
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.
Summary
Add a new DRT operation (
oom) that induces memory pressure on arandomly selected node by filling
/dev/shmwith a ballast file,leaving a configurable reserve (3 GiB) to keep the node alive long
enough to capture heap profiles.
/dev/shmto 90% of total RAM to allow sufficient fillpeer health, and queries for unavailable ranges every 30s
/dev/shmsizing, andrestarts the node via
cockroach.shif it became unresponsiveoperations
Epic: none