# Kibana: Kibana's memory limit won't change. Even to default **URL:** \ **Category:** Kibana\ **Created:** [April 15, 2021, 7:38am UTC](https://discuss.elastic.co/t/kibana-kibanas-memory-limit-wont-change-even-to-default/270197 "2021-04-15T07:38:12Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![ade.syseng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ade.syseng/32/122286_2.png) [@ade.syseng](https://discuss.elastic.co/u/ade.syseng)\ **Post date:** [April 15, 2021, 7:38am UTC](https://discuss.elastic.co/t/kibana-kibanas-memory-limit-wont-change-even-to-default/270197/1 "2021-04-15T07:38:12Z")
Hi, I'm just upgraded Kibana to 7.12. And I noticed Kibana's memory limit configured at 4GB according to Stack Monitoring. ![kibana](https://us1.discourse-cdn.com/elastic/original/3X/7/8/7858523377bbade4b5c70fff8a3be6912270a410.png) So then I set the memory limit to 2GB, it was a success. Sometime later, due to web server limitation, I changed Kibana's listen port to 80 and 443 to access Kibana directly without a web server and enabled these configurations to allow Kibana to listen on lower port number: > setcap cap\_net\_bind\_service=+epi /usr/share/kibana/bin/kibana > setcap cap\_net\_bind\_service=+epi /usr/share/kibana/bin/kibana-plugin > setcap cap\_net\_bind\_service=+epi /usr/share/kibana/bin/kibana-keystore > setcap cap\_net\_bind\_service=+epi /usr/share/kibana/bin/kibana-encryption-keys > setcap cap\_net\_bind\_service=+epi /usr/share/kibana/node/bin/node Then I noticed Kibana's memory limit changed to 4GB again ignored my configuration. I have tried to change the memory limit in: > /etc/sysconfig/kibana > /etc/kibana/node.options Even forcing in: > /usr/share/kibana/bin/kibana > /etc/systemd/system/kibana.service None of them was working. Kibana memory limit still configured at 4GB. I also tried to delete the memory limit configuration "_--max-old-space-size=2048_", but still not working. According to this [guidance](https://www.elastic.co/guide/en/kibana/current/production.html#memory), Kibana's default memory limit at 1.4GB. Any suggestion or solution for this issue? Regards, Ade ---
**Author:** ![ade.syseng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ade.syseng/32/122286_2.png) [@ade.syseng](https://discuss.elastic.co/u/ade.syseng)\ **Post date:** [April 19, 2021, 4:33am UTC](https://discuss.elastic.co/t/kibana-kibanas-memory-limit-wont-change-even-to-default/270197/2 "2021-04-19T04:33:14Z")
Anyone can help my problem? Thank you! ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [April 19, 2021, 6:03pm UTC](https://discuss.elastic.co/t/kibana-kibanas-memory-limit-wont-change-even-to-default/270197/3 "2021-04-19T18:03:47Z")
@jbudz - can you plz help when you get a chance, Thanks ---
**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\ **Post date:** [April 19, 2021, 9:24pm UTC](https://discuss.elastic.co/t/kibana-kibanas-memory-limit-wont-change-even-to-default/270197/4 "2021-04-19T21:24:40Z")
Hey Ade, Can you share the permissions set for /etc/kibana/node.options? I'm wondering if the file isn't readable by the `kibana` user. ---
**Author:** ![ade.syseng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ade.syseng/32/122286_2.png) [@ade.syseng](https://discuss.elastic.co/u/ade.syseng)\ **Post date:** [April 20, 2021, 3:03am UTC](https://discuss.elastic.co/t/kibana-kibanas-memory-limit-wont-change-even-to-default/270197/5 "2021-04-20T03:03:40Z")
Hi @jbudz , Thanks for the respond. Here's the permissions: ![kibana](https://us1.discourse-cdn.com/elastic/original/3X/0/5/053dd6702f701e30e5adce6d430af83b068caa6b.png) Any clue? permissions seems correct. ---
**Author:** ![ade.syseng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ade.syseng/32/122286_2.png) [@ade.syseng](https://discuss.elastic.co/u/ade.syseng)\ **Post date:** [April 23, 2021, 1:44am UTC](https://discuss.elastic.co/t/kibana-kibanas-memory-limit-wont-change-even-to-default/270197/6 "2021-04-23T01:44:36Z")
Hi @jbudz, I think I found a temporary solution to my problem. All I need to do is to add the memory limit configuration "_--max-old-space-size=2048_" in: > /usr/share/kibana/bin/kibana in this line, like this: > NODE\_OPTIONS="--no-warnings --max-http-header-size=65536 --tls-min-v1.0 $KBN\_NODE\_OPTS $NODE\_OPTIONS" NODE\_ENV=production exec "${NODE}" _ **--max-old-space-size=2048** _ "${DIR}/src/cli/dist" ${@} and here's the result: ![kibs](https://us1.discourse-cdn.com/elastic/original/3X/a/3/a345532a6b5fcd09e60a26a73708d3ce2576046a.png) but I think this is not standard to set Kibana's memory limit. Any thought? ---
**Author:** ![ade.syseng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ade.syseng/32/122286_2.png) [@ade.syseng](https://discuss.elastic.co/u/ade.syseng)\ **Post date:** [May 3, 2021, 4:21am UTC](https://discuss.elastic.co/t/kibana-kibanas-memory-limit-wont-change-even-to-default/270197/7 "2021-05-03T04:21:04Z")
hmm.. Anyone? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 31, 2021, 4:21am UTC](https://discuss.elastic.co/t/kibana-kibanas-memory-limit-wont-change-even-to-default/270197/8 "2021-05-31T04:21:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed. ---
**Author:** ![Guillaume\_Dufrenne](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guillaume_dufrenne/32/103641_2.png) [@Guillaume\_Dufrenne](https://discuss.elastic.co/u/Guillaume_Dufrenne)\ **Post date:** [July 17, 2025, 2:17pm UTC](https://discuss.elastic.co/t/kibana-kibanas-memory-limit-wont-change-even-to-default/270197/9 "2025-07-17T14:17:44Z")
It's a [nodeJS bug](https://github.com/nodejs/node/issues/37588), there is no direct solution on the Kibana side The workaround you mentioned is valid.