Configure heap dump path out of the box#26755
Merged
jasontedor merged 1 commit intoelastic:masterfrom Sep 22, 2017
Merged
Conversation
The JVM defaults to dumping the heap to the working directory of Elasticsearch. For the RPM and Debian packages, this location is /usr/share/elasticsearch. This directory is not writable by the elasticsearch user, so by default heap dumps in this situation are lost. This commit modifies the packaging for the RPM and Debian packages to set the heap dump path to /var/lib/elasticsearch as the default location for dumping the heap. This location is writable by the elasticsearch user by default. We add documentation of this important setting if /var/lib/elasticsearch is not suitable for receiving heap dumps.
jasontedor
added a commit
that referenced
this pull request
Sep 22, 2017
The JVM defaults to dumping the heap to the working directory of Elasticsearch. For the RPM and Debian packages, this location is /usr/share/elasticsearch. This directory is not writable by the elasticsearch user, so by default heap dumps in this situation are lost. This commit modifies the packaging for the RPM and Debian packages to set the heap dump path to /var/lib/elasticsearch as the default location for dumping the heap. This location is writable by the elasticsearch user by default. We add documentation of this important setting if /var/lib/elasticsearch is not suitable for receiving heap dumps. Relates #26755
jasontedor
added a commit
that referenced
this pull request
Sep 22, 2017
The JVM defaults to dumping the heap to the working directory of Elasticsearch. For the RPM and Debian packages, this location is /usr/share/elasticsearch. This directory is not writable by the elasticsearch user, so by default heap dumps in this situation are lost. This commit modifies the packaging for the RPM and Debian packages to set the heap dump path to /var/lib/elasticsearch as the default location for dumping the heap. This location is writable by the elasticsearch user by default. We add documentation of this important setting if /var/lib/elasticsearch is not suitable for receiving heap dumps. Relates #26755
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
6 participants
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.
The JVM defaults to dumping the heap to the working directory of Elasticsearch. For the RPM and Debian packages, this location is /usr/share/elasticsearch. This directory is not writable by the elasticsearch user, so by default heap dumps in this situation are lost. This commit modifies the packaging for the RPM and Debian packages to set the heap dump path to /var/lib/elasticsearch as the default location for dumping the heap. This location is writable by the elasticsearch user by default. We add documentation of this important setting if /var/lib/elasticsearch is not suitable for receiving heap dumps.
Closes #26665