Skip to content
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

Better way to set max-old-space-size #6727

Closed
PSiAU opened this issue Apr 1, 2016 · 3 comments
Closed

Better way to set max-old-space-size #6727

PSiAU opened this issue Apr 1, 2016 · 3 comments
Labels
release_note:enhancement Team:Operations Team label for Operations Team

Comments

@PSiAU
Copy link

PSiAU commented Apr 1, 2016

As far as I know, the only place to set max-old-space-size is via NODE_OPTIONS in /opt/kibana/bin/kibana. This is on Debian with kibana installed via the package.
This file gets overwritten during a version upgrade which necessitates updating the file manually each time.
Surely there must be a better way to set max-old-space-size without it getting overwritten after every upgrade?

@epixa
Copy link
Contributor

epixa commented Apr 1, 2016

Given that we really want node to be an implementation detail rather and we recommend that this be set, I think this does need to be configurable somehow via kibana itself.

@zerkms
Copy link

zerkms commented May 27, 2016

Btw, I recently filled #7237 and I think they both address the same problem from different angles.

Please do not add another parameter, but use the standard OS tools (as I suggested in the other issue)

@tylersmalley
Copy link
Contributor

Closing, this can now be done with a node.options file in the configuration directory.

https://www.elastic.co/guide/en/kibana/7.9/production.html#memory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:enhancement Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

5 participants