Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
9.4.1
-
None
-
None
Description
when Xmx and Xms heap size are equal everything is correct.
If Xms is smaller (or not set at all), values in Dashboard and cloud are inconsistent e.g.
Xms not set, Xms=512m, after a short time:
Dashboard->JVM Memory
JVM-Memory 20%
512.00 MB
102.00 MB
Cloud->Nodes->Heap
100%
Max: 102.0Mb
Used: 102.0Mb
I think what we want here in cloud->nodes->heap is also the currentSize/maxHeapSize and not the currentSize/currentCommitedMemory.
When using relative small Xms settings together with garabge collector, uncommiting memory (ZGC default) the value is 100% most of time (looks dangerous, marked red and may confuse). I noticed this first when trying to use MaxRAMPercentage instead of Xms/Xmx to use the same config on different cloud sizes.