-
Couldn't load subscription status.
- Fork 1k
Disable container support in opensearch test containers #15022
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
Conversation
| // limit memory usage and disable Log4j JMX to avoid cgroup detection issues in containers | ||
| opensearch.withEnv( | ||
| "OPENSEARCH_JAVA_OPTS", | ||
| "-Xmx256m -Xms256m -Dlog4j2.disableJmx=true -Dlog4j2.disable.jmx=true -XX:-UseContainerSupport"); |
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.
i dont know what version of log4j is in use, so added both configs
https://logging.apache.org/log4j/2.x/manual/jmx.html
https://logging.apache.org/log4j/2.3.x/manual/jmx.html
|
@jaydeluca heads up looks like also impacting elasticsearch |
There have been a lot of flaky opensearch tests today (example)
I figured we could try disabling container support (-XX:-UseContainerSupport) and Log4j JMX to fix some NullPointerExceptions in CgroupV2Subsystem.getInstance() during container startup.
Not sure if this will fix it, but didnt seem like it could hurt. Seems like it helped for someone else
Hopefully resolves #15024
Some stack traces: