[
https://issues.apache.org/jira/browse/SOLR-14607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325726#comment-17325726
]
Alessandro Benedetti commented on SOLR-14607:
---------------------------------------------
I didn't have time to check how it works in details, but from the documentation:
https://solr.apache.org/guide/8_8/common-query-parameters.html#timeallowed-parameter
It seems to me that:
0 - is acceptable
1 - is acceptable, this means we don't start re-ranking if the time is already
expired, the behaviour pre-reRanking is not changed
6 - is acceptable, as I already stated reRanking in my opinion is all or
nothing (and this seems in line with the current implementation of others query
phases, i.e.
when reRanking is supposed to start, you check the timeAllowed, if it is not
expired yet, you do the reranking full.
when reRanking is supposed to start, you check the timeAllowed, if it is
expired, you don't rerank at all.
I agree with [~cpoerschke] on the generic rerank query parser question, it
would be useful to investigate how it behaves right now [~limingnihao]
> LTR Query, timeAllowed parameter causes a timeout exception with no result
> --------------------------------------------------------------------------
>
> Key: SOLR-14607
> URL: https://issues.apache.org/jira/browse/SOLR-14607
> Project: Solr
> Issue Type: Improvement
> Components: contrib - LTR
> Affects Versions: main (9.0)
> Reporter: Dawn
> Priority: Minor
> Attachments: SOLR-14607-poc.patch
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> When using the LTR, open timeAllowed parameter, LTR feature of query may call
> 'ExitableFilterAtomicReader.CheckAndThrow' timeout checks.
> If a timeout occurs at this point, the exception ExitingReaderException is
> thrown, Lead to null result.
> Exception information:
> {code:java}
> The request took too long to iterate over terms. Timeout: timeoutAt:
> 50321611131050 (System.nanoTime(): 50321639573838),
> TermsEnum=org.apache.lucene.codecs.blocktree.SegmentTermsEnum@62eaeeaa
> {code}
>
> Can hold this exception in the LTR, returning partial results rather than
> null.
> This exception occurs in two places:
> 1. 'LTRScoringQuery.CreateWeight' or 'LTRScoringQuery.createWeightsParallel'.
> Here is the loading stage, timeout directly end is acceptable.
> 2. 'ModelWeight.scorer'. This is a stage that evaluates each Doc and can
> catch the exception, returns the computed document.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
