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/02/07 02:50:00 UTC
[jira] [Commented] (SOLR-17141) Create CpuQueryLimit implementation
[ https://issues.apache.org/jira/browse/SOLR-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815068#comment-17815068 ]
Gus Heck commented on SOLR-17141:
---------------------------------
Probably need to coordinate in some fashion between SOLR-17141 and SOLR-16986. It would be bad if the logged value varied from the value observed by CpuQueryLimit and created the impression that the limit was not being respected, or terminating early....
> Create CpuQueryLimit implementation
> -----------------------------------
>
> Key: SOLR-17141
> URL: https://issues.apache.org/jira/browse/SOLR-17141
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This class will use `getThreadCpuTime` to determine when to signal `shouldExit`.
--
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