[
https://issues.apache.org/jira/browse/SOLR-17203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828420#comment-17828420
]
ASF subversion and git services commented on SOLR-17203:
--------------------------------------------------------
Commit bdc4a4dc4fc36a7a2ceed44f3b29f84455eedb1e in solr's branch
refs/heads/branch_9x from Gus Heck
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=bdc4a4dc4fc ]
SOLR-17203 fix calculation for CpuAllowedLimit (#2347) (#2357)
(cherry picked from commit f67b7183cc57638589b2303185237d6612fb9ad3)
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
