Gus Heck created SOLR-17203:
-------------------------------
Summary: 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
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-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
