Add hint to allocate more memory if Elasticsearch crashes #1
Conversation
This file contains 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
…arch.md When creating Elasticsearch indicies, the process could crash if there is not enough memory allocated to the JVM runtime. This commit adds a hint for administrators to try to allocate more memory to Elasticsearch if they're experiencing out-of-memory issues.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When creating Elasticsearch indicies, the process could crash if there is not enough memory allocated to the JVM runtime.
This commit adds a hint (and a step-by-step-guide) for administrators to try to allocate more memory to Elasticsearch if they're experiencing out-of-memory issues.
(I had a hard time troubleshooting this issue and I think others could benefit from this solution.)
Feedback and suggestions for improvement are welcome.