[
https://issues.apache.org/jira/browse/SOLR-17129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Wahlen updated SOLR-17129:
--------------------------------
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 differnt cloud
sizes.
was:
when Xmx and Xms heap size 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 differnt cloud
sizes.
> solr webinterface (cloud->heap) 100% false positive
> ---------------------------------------------------
>
> Key: SOLR-17129
> URL: https://issues.apache.org/jira/browse/SOLR-17129
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 9.4.1
> Reporter: Bernd Wahlen
> Priority: Minor
>
> 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 differnt
> cloud sizes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
