[
https://issues.apache.org/jira/browse/SOLR-16605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653689#comment-17653689
]
Shawn Heisey commented on SOLR-16605:
-------------------------------------
If I just do the javascript change, that seems to produce the same results as
the whole patch. Sometimes it shows a nonzero CPU usage, mostly it shows 0%.
I will go ahead and commit the javascript change shortly, because what's there
currently is wrong, as the returned value from the bean is in the range of 0-1,
not 0-100.
My little test program looks like the processCpuLoad method is returning the
correct value on every run, so I am very confused about why Solr is reporting
0% most of the time.
> 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]
