[
https://issues.apache.org/jira/browse/SOLR-17018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779837#comment-17779837
]
Ahmad Abdelghany edited comment on SOLR-17018 at 10/26/23 10:42 AM:
--------------------------------------------------------------------
Thanks [~dsmiley], just to confirm my understanding:
* LTR does not respect timeAllowed in any Solr version.
* {{ExitableDirectoryReader}} that was the default until 9.3 respects
timeAllowed in core query processing + spellcheck + faceting but not LTR.
* {{TimeLimitingBulkScorer}} that is the new default in 9.3 respects
timeAllowed in query processing only. So it won't help, it could only make OOM
more likely, not withstanding the performance improvement.
was (Author: JIRAUSER302634):
Thanks [~dsmiley], just to confirm my understanding is that:
* LTR does not respect timeAllowed in any version.
* {{ExitableDirectoryReader}} that was the default until 9.3 respects
timeAllowed in core query processing + spellcheck + faceting but not LTR.
* {{TimeLimitingBulkScorer}} that is the new default in 9.3 only respects
timeAllowed in query processing only. So it won't help, it could only make OOM
more likely, not withstanding the performance improvement.
> LTR queries producing out of memory issues
> ------------------------------------------
>
> Key: SOLR-17018
> URL: https://issues.apache.org/jira/browse/SOLR-17018
> Project: Solr
> Issue Type: Improvement
> Components: contrib - LTR, ltr
> Affects Versions: 9.1.1
> Reporter: rajanimaski
> Priority: Major
> Labels: ltr
> Attachments: image-2023-10-11-14-38-43-351.png
>
>
> LTR queries are producing oom and looks like the issue is same as what is
> described on this SOLR-5986. I think this happens because LTR component does
> not implement `timeAllowed`. During peak traffic hours, when 80% of resources
> are in use, one expensive LTR query that either has more terms or paginated
> with start>=500 are not ceased and hence leading to full heap usage, invoking
> full GC, and reporting an oom. I do see queries with ltr param are taking
> more than 15 seconds which seems like is the reason for oom issue, it is
> during this time interval the tenured(old generation) heap also gets filled
> up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
