-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Add availability info for default heap dump path change #131713
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
base: main
Are you sure you want to change the base?
Conversation
Pinging @elastic/es-docs (Team:Docs) |
🔍 Preview links for changed docs |
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.
Looks good, but the change is also in 8.19
By default, {{es}} configures the JVM to dump the heap on out of memory exceptions to the default logs directory. On [RPM](docs-content://deploy-manage/deploy/self-managed/install-elasticsearch-with-rpm.md) and [Debian](docs-content://deploy-manage/deploy/self-managed/install-elasticsearch-with-debian-package.md) packages, the logs directory is `/var/log/elasticsearch`. On [Linux and MacOS](docs-content://deploy-manage/deploy/self-managed/install-elasticsearch-from-archive-on-linux-macos.md) and [Windows](docs-content://deploy-manage/deploy/self-managed/install-elasticsearch-with-zip-on-windows.md) distributions, the `logs` directory is located under the root of the {{es}} installation. | ||
Depending on your stack version, {{es}} configures the JVM to dump the heap on out of memory exceptions to the following location by default: | ||
|
||
* {applies_to}`stack: ga 9.1` The default logs directory |
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.
This should also include 8.19?
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.
this docs set only applies to 9.0+, but I agree that it is confusing. let me see if there's something I'm able to do.
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.
verified that we need to keep the 8.x and 9.x docs separate - this info should be manually backported into the asciidoc docs in the 8.19 branch.
will likely be doing a validation pass that the changes that are making it into 8.19 were appropriately ported but haven't gotten there yet :)
Followup to #124966
This PR adds availability information for the change to the default jvm heap dump path. used tabs to provide detailed path information for both logs and data
Docs are now cumulative, which means that we need to clearly tag changes introduced in each version going forward, and keep docs valid for users still using older versions.