[
https://issues.apache.org/jira/browse/SOLR-18186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070298#comment-18070298
]
Ravi Ranjan Jha commented on SOLR-18186:
----------------------------------------
Raised a PR for fixing this issue - https://github.com/apache/solr/pull/4257
> Solr heap used percentage uses committed heap instead of max heap which
> raises false alarm
> -------------------------------------------------------------------------------------------
>
> Key: SOLR-18186
> URL: https://issues.apache.org/jira/browse/SOLR-18186
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
> Affects Versions: 10.0, 9.10.1
> Reporter: Ravi Ranjan Jha
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2026-04-01-15-52-26-883.png,
> image-2026-04-01-15-54-29-256.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Solr heap used percentage uses committed heap instead of max heap. Ideally it
> should use configured max heap size for the calculation.
> At this point, it causes unnecessary concern to the users can see a high
> percentage in red even for low heap usage.
> As an example in this image it shows the heap usage as 89% in red for 6.9 GB
> usage because committed memory is 7.6 GB but the actually configured max heap
> (-Xmx) is 12GB. This computation should use configured max heap size of 12 GB
> instead which will show the actual status of the node heap usage.
> !image-2026-04-01-15-52-26-883.png!
>
> !image-2026-04-01-15-54-29-256.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
