You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Gus Heck (Jira)" <ji...@apache.org> on 2024/03/19 15:44:00 UTC
[jira] [Resolved] (SOLR-17203) CPU not calculated correctly in ThreadCpuTimer
[ https://issues.apache.org/jira/browse/SOLR-17203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gus Heck resolved SOLR-17203.
-----------------------------
Fix Version/s: main (10.0)
9.6.0
Resolution: Fixed
> CPU not calculated correctly in ThreadCpuTimer
> ----------------------------------------------
>
> Key: SOLR-17203
> URL: https://issues.apache.org/jira/browse/SOLR-17203
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Query Limits
> Affects Versions: main (10.0), 9.6.0
> Reporter: Gus Heck
> Assignee: Gus Heck
> Priority: Major
> Fix For: main (10.0), 9.6.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Naming is hard, and the initial implementation seems to have stumbled on a method naming confusion with the effect that it was only possible to hit a cpu time out shortly after a new thread is created (which is true when the tests run, and thus the test was passing). Essentially it was grabbing an elapsed time for the timer and, treating it as the total time for the thread.
> Fixed locally, will submit PR soon...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org