Skip to content

feat: JVM fault injection, phase one #748

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bjoky
Copy link
Contributor

@bjoky bjoky commented Apr 16, 2025

What this PR does / why we need it:

This is the first pull request in a series of pull requests that will implement JVM fault injection. For more background, please read the proposal here: https://github.com/litmuschaos/litmus/blob/master/proposals/jvm-fault-injection.md

This is a java tool that can consume memory or CPU in a running JVM. See the README.md file for more details.

Special notes for your reviewer:

This pull request only contains the Java code part of the fault injection. The intention is to invoke this from helper-pod running in the same node as the target JVM.

Future pull requests will contain: building a jar-file and including it in the litmus-go image and the code for two experiments (cpu and memory allocation) in go code that invokes the java tool.

Checklist:

  • Fixes #
  • PR messages has document related information
  • Labelled this PR & related issue with breaking-changes tag
  • PR messages has breaking changes related information
  • Labelled this PR & related issue with requires-upgrade tag
  • PR messages has upgrade related information
  • Commit has unit tests
  • Commit has integration tests
  • E2E run Required for the changes

Signed-off-by: Björn Kylberg <[email protected]>
@bjoky bjoky changed the title JVM fault injection, phase one feat: JVM fault injection, phase one Apr 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant