[ 
https://issues.apache.org/jira/browse/SOLR-14607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299793#comment-17299793
 ] 

Christine Poerschke commented on SOLR-14607:
--------------------------------------------

Based on the artificial scenario's stacktrace above I have some thoughts, 
complimentary to your [https://github.com/apache/solr/pull/8] changes, on the 
implications of different ways of handling the exceptions. Will add comments on 
the pull request shortly. Thank you.

> 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: 1.5h
>  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)

Reply via email to