Elasticsearch 2.4 jvm.options ignored on MacOS Mojave (Homebrew install)
I've installed ElasticSearch 2.4 on my mac via HomeBrew. I'm trying to see if I can increase the JVM heap size for ElasticSearch.
I changed the following lines (to set the heap size to 8 gigs) in /usr/local/etc/elasticsearch/jvm.options
-Xms8g
-Xmx8g
I then restart the service using brew services restart elasticsearch@2.4 and run curl localhost:9200/_nodes/stats/jvm?pretty to check the JVM size but I get back:
"mem" : {
"heap_used_in_bytes" : 144690472,
"heap_used_percent" : 13,
"heap_committed_in_bytes" : 259522560,
"heap_max_in_bytes" : 1038876672,
"non_heap_used_in_bytes" : 62484680,
"non_heap_committed_in_bytes" : 65093632,
...
Why are my Xms8g and Xmx8g flags being ignored in jvm.options, and what should I do to make elsaticsearch respect them?
I've been basing my actions on: How to change Elasticsearch max memory size
java elasticsearch jvm homebrew elasticsearch-2.4
asked Jan 3 at 11:20
RP-3RP-3
10511
add a comment |
I've installed ElasticSearch 2.4 on my mac via HomeBrew. I'm trying to see if I can increase the JVM heap size for ElasticSearch.
I changed the following lines (to set the heap size to 8 gigs) in /usr/local/etc/elasticsearch/jvm.options
-Xms8g
-Xmx8g
I then restart the service using brew services restart elasticsearch@2.4 and run curl localhost:9200/_nodes/stats/jvm?pretty to check the JVM size but I get back:
"mem" : {
"heap_used_in_bytes" : 144690472,
"heap_used_percent" : 13,
"heap_committed_in_bytes" : 259522560,
"heap_max_in_bytes" : 1038876672,
"non_heap_used_in_bytes" : 62484680,
"non_heap_committed_in_bytes" : 65093632,
...
Why are my Xms8g and Xmx8g flags being ignored in jvm.options, and what should I do to make elsaticsearch respect them?
I've been basing my actions on: How to change Elasticsearch max memory size
java elasticsearch jvm homebrew elasticsearch-2.4
asked Jan 3 at 11:20
RP-3RP-3
10511
add a comment |
I've installed ElasticSearch 2.4 on my mac via HomeBrew. I'm trying to see if I can increase the JVM heap size for ElasticSearch.
I changed the following lines (to set the heap size to 8 gigs) in /usr/local/etc/elasticsearch/jvm.options
-Xms8g
-Xmx8g
I then restart the service using brew services restart elasticsearch@2.4 and run curl localhost:9200/_nodes/stats/jvm?pretty to check the JVM size but I get back:
"mem" : {
"heap_used_in_bytes" : 144690472,
"heap_used_percent" : 13,
"heap_committed_in_bytes" : 259522560,
"heap_max_in_bytes" : 1038876672,
"non_heap_used_in_bytes" : 62484680,
"non_heap_committed_in_bytes" : 65093632,
...
Why are my Xms8g and Xmx8g flags being ignored in jvm.options, and what should I do to make elsaticsearch respect them?
I've been basing my actions on: How to change Elasticsearch max memory size
java elasticsearch jvm homebrew elasticsearch-2.4
asked Jan 3 at 11:20
RP-3RP-3
10511
I've installed ElasticSearch 2.4 on my mac via HomeBrew. I'm trying to see if I can increase the JVM heap size for ElasticSearch.
I changed the following lines (to set the heap size to 8 gigs) in /usr/local/etc/elasticsearch/jvm.options
-Xms8g
-Xmx8g
I then restart the service using brew services restart elasticsearch@2.4 and run curl localhost:9200/_nodes/stats/jvm?pretty to check the JVM size but I get back:
"mem" : {
"heap_used_in_bytes" : 144690472,
"heap_used_percent" : 13,
"heap_committed_in_bytes" : 259522560,
"heap_max_in_bytes" : 1038876672,
"non_heap_used_in_bytes" : 62484680,
"non_heap_committed_in_bytes" : 65093632,
...
Why are my Xms8g and Xmx8g flags being ignored in jvm.options, and what should I do to make elsaticsearch respect them?
I've been basing my actions on: How to change Elasticsearch max memory size
java elasticsearch jvm homebrew elasticsearch-2.4
java elasticsearch jvm homebrew elasticsearch-2.4
asked Jan 3 at 11:20
RP-3RP-3
10511
asked Jan 3 at 11:20
RP-3RP-3
10511
asked Jan 3 at 11:20
RP-3RP-3
10511
asked Jan 3 at 11:20
RP-3RP-3
10511
asked Jan 3 at 11:20
RP-3RP-3
10511
10511
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Figured it out!
You need to change the environment variables passed through the plist used to launch elasticsearch.
In /usr/local/Cellar/elasticsearch@2.4/2.4.6/homebrew.mxcl.elasticsearch@2.4.plist, under the <key>EnvironmentVariables</key> key, add:
<dict>
<key>ES_HEAP_SIZE</key>
<string>2g</string>
</dict>
Beware, there's another plist that exists in ~/Library/LaunchAgents/homebrew.mxcl.elasticsearch.plist. Changing this does nothing since it gets overwritten by brew services on restart.
Also of note, there are two jvm.options files to do with ElasticSearch visible on your system:
/usr/local/Cellar/elasticsearch@2.4/2.4.6/libexec/config/usr/local/etc/elasticsearch/jvm.options
It looks like one of these is just a symlink to the other, and changing the memory flags in either of them does absolutely nothing.
answered Jan 3 at 20:20
RP-3RP-3
10511
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54021316%2felasticsearch-2-4-jvm-options-ignored-on-macos-mojave-homebrew-install%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Figured it out!
You need to change the environment variables passed through the plist used to launch elasticsearch.
In /usr/local/Cellar/elasticsearch@2.4/2.4.6/homebrew.mxcl.elasticsearch@2.4.plist, under the <key>EnvironmentVariables</key> key, add:
<dict>
<key>ES_HEAP_SIZE</key>
<string>2g</string>
</dict>
Beware, there's another plist that exists in ~/Library/LaunchAgents/homebrew.mxcl.elasticsearch.plist. Changing this does nothing since it gets overwritten by brew services on restart.
Also of note, there are two jvm.options files to do with ElasticSearch visible on your system:
/usr/local/Cellar/elasticsearch@2.4/2.4.6/libexec/config/usr/local/etc/elasticsearch/jvm.options
It looks like one of these is just a symlink to the other, and changing the memory flags in either of them does absolutely nothing.
answered Jan 3 at 20:20
RP-3RP-3
10511
add a comment |
Figured it out!
You need to change the environment variables passed through the plist used to launch elasticsearch.
In /usr/local/Cellar/elasticsearch@2.4/2.4.6/homebrew.mxcl.elasticsearch@2.4.plist, under the <key>EnvironmentVariables</key> key, add:
<dict>
<key>ES_HEAP_SIZE</key>
<string>2g</string>
</dict>
Beware, there's another plist that exists in ~/Library/LaunchAgents/homebrew.mxcl.elasticsearch.plist. Changing this does nothing since it gets overwritten by brew services on restart.
Also of note, there are two jvm.options files to do with ElasticSearch visible on your system:
/usr/local/Cellar/elasticsearch@2.4/2.4.6/libexec/config/usr/local/etc/elasticsearch/jvm.options
It looks like one of these is just a symlink to the other, and changing the memory flags in either of them does absolutely nothing.
answered Jan 3 at 20:20
RP-3RP-3
10511
add a comment |
Figured it out!
You need to change the environment variables passed through the plist used to launch elasticsearch.
In /usr/local/Cellar/elasticsearch@2.4/2.4.6/homebrew.mxcl.elasticsearch@2.4.plist, under the <key>EnvironmentVariables</key> key, add:
<dict>
<key>ES_HEAP_SIZE</key>
<string>2g</string>
</dict>
Beware, there's another plist that exists in ~/Library/LaunchAgents/homebrew.mxcl.elasticsearch.plist. Changing this does nothing since it gets overwritten by brew services on restart.
Also of note, there are two jvm.options files to do with ElasticSearch visible on your system:
/usr/local/Cellar/elasticsearch@2.4/2.4.6/libexec/config/usr/local/etc/elasticsearch/jvm.options
It looks like one of these is just a symlink to the other, and changing the memory flags in either of them does absolutely nothing.
answered Jan 3 at 20:20
RP-3RP-3
10511
Figured it out!
You need to change the environment variables passed through the plist used to launch elasticsearch.
In /usr/local/Cellar/elasticsearch@2.4/2.4.6/homebrew.mxcl.elasticsearch@2.4.plist, under the <key>EnvironmentVariables</key> key, add:
<dict>
<key>ES_HEAP_SIZE</key>
<string>2g</string>
</dict>
Beware, there's another plist that exists in ~/Library/LaunchAgents/homebrew.mxcl.elasticsearch.plist. Changing this does nothing since it gets overwritten by brew services on restart.
Also of note, there are two jvm.options files to do with ElasticSearch visible on your system:
/usr/local/Cellar/elasticsearch@2.4/2.4.6/libexec/config/usr/local/etc/elasticsearch/jvm.options
It looks like one of these is just a symlink to the other, and changing the memory flags in either of them does absolutely nothing.
answered Jan 3 at 20:20
RP-3RP-3
10511
answered Jan 3 at 20:20
RP-3RP-3
10511
answered Jan 3 at 20:20
RP-3RP-3
10511
answered Jan 3 at 20:20
RP-3RP-3
10511
10511
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54021316%2felasticsearch-2-4-jvm-options-ignored-on-macos-mojave-homebrew-install%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
