You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This chart will automatically calculate Java heap size from given resources.requests.memory value. If you want to specify number of heap size, you can set graylog.heapSize to your desired value. The graylog.heapSize value must be in JVM -Xmx format.
So, we all incorrectly assumed this meant that if we do not specify a graylog.heapSize in our values, it will default to our resources.requests.memory value, which we are specifying like so in our values file:
To my surprise, I saw Graylog regularly consuming > 13GB of memory. It turns out, the documentation is incorrect, because 16g is hard-coded to the default values here:
In the documentation, it states:
So, we all incorrectly assumed this meant that if we do not specify a
graylog.heapSize
in our values, it will default to ourresources.requests.memory
value, which we are specifying like so in our values file:To my surprise, I saw Graylog regularly consuming > 13GB of memory. It turns out, the documentation is incorrect, because
16g
is hard-coded to the default values here:charts/charts/graylog/values.yaml
Lines 369 to 372 in 0c8a9a4
And so this if condition is used:
charts/charts/graylog/templates/statefulset.yaml
Lines 111 to 115 in 0c8a9a4
We had to explicitly add
heapSize
to our values file:In order to get Graylog to stop consuming so much memory.
By the way, love the chart, thank you for it! 🙏
The text was updated successfully, but these errors were encountered: