-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Add replay diagnostic dir to system jvm options #103535
Conversation
When hotspot encounters an error, it will emite a log file which can be used for reproducing the error. This file is dumped to /tmp by default. This commit configures the replay file to be alongside the hs_err file.
Pinging @elastic/es-core-infra (Team:Core/Infra) |
Hi @rjernst, I've created a changelog YAML for you. |
Note to reviewers: I've intentionally not put this configuration in the same place as hs_err in the jvm.options files. This is because every change to that file can cause conflicts to users installing ES with package managers. Instead, I think we should focus on adding new (and maybe moving existing) options to the SystemJvmOptions. |
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.
LGTM
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.
Good to capture this file. LGTM
When hotspot encounters an error, it will emite a log file which can be used for reproducing the error. This file is dumped to /tmp by default. This commit configures the replay file to be alongside the hs_err file.