Remove conflicting memory allocation instructions for Elasticsearch - #1943
Open
smiba wants to merge 1 commit into
Open
Remove conflicting memory allocation instructions for Elasticsearch#1943smiba wants to merge 1 commit into
smiba wants to merge 1 commit into
Conversation
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
1 participant
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.
PRs #1456 and #1468 add conflicting instructions to the Elasticsearch page when it comes to allocating memory
Initially we start with 16GB (pre) 24GB (max) at
/etc/elasticsearch/jvm.options.d/limit-ram.optionsBut later we describe that if mastodon crashes during indices we should allocate "more" memory: 2GB (max) at
/etc/elasticsearch/jvm.options.d/ram.optionsThis means that someone following this tutorial will actually reduce their memory allocation, and have their memory allocation defined twice, not sure which one is picked or if this works at all.
This PR removes the double instructions
Additionally I think the default of 24GB memory max is way too much, but out of scope of this PR :)