[
https://issues.apache.org/jira/browse/SOLR-16605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653734#comment-17653734
]
Shawn Heisey commented on SOLR-16605:
-------------------------------------
I have not been able to figure out what is happening. Added some logging to
the MetricsUtil class, and the metrics processCpuLoad entry in the metrics bean
does not match when the admin UI says something other than 0%. When the UI
says 0%, the value is 0.0. Have to reload the page several times to get it
saying anything other than 0%.
In my test program, the mx bean's processCpuLoad and systemCpuLoad entries
appear to be correct. But for some reason when Solr does it the value is
wrong. I suspect that something happens deep within Solr's metrics classes
that I don't understand.
> CPU in UI cloud->nodes is always 0%, even when Solr is very busy.
> -----------------------------------------------------------------
>
> Key: SOLR-16605
> URL: https://issues.apache.org/jira/browse/SOLR-16605
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
> Affects Versions: 9.1
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Major
> Attachments: fixcpuadminui-1.patch
>
>
> The Cloud->Nodes section of the admin UI is always reporting 0% CPU even on
> very busy Solr nodes. I thought the attached patch would fix t, but it
> doesn't seem to be working. Instead of always 0%, it now shows an occasional
> 50% or 100%... and even rarer is a different percentage like 84% or 17%. The
> Solr process at that time was usng about 180% CPU (two CPUs in AWS instance).
> Using OperatingSystemMXBean from com.sun instead of java.lang seemed to work
> fine in a quick test program, but it's not working in Solr. I am trying this
> on Ubuntu Linux with OpenJDK 17 and 11.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
