[
https://issues.apache.org/jira/browse/LUCENE-8989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943296#comment-16943296
]
Atri Sharma commented on LUCENE-8989:
-------------------------------------
bq. Hmm, that is a good point – maybe we should not handle this exception and
let it throw?
I would still argue that the default case should be to handle the exception and
let the query execute gracefully. The case where executor has been erratically
shut down is a good point, but for edges like this, we should probably override
IndexSearcher's default behaviour. If it helps, we could potentially introduce
a toggle which is enabled by default and indicates that IndexSearcher will
perform the graceful handling, and if the user wishes the error to propagate,
just call a new API method to disable the toggle?
> IndexSearcher Should Handle Rejection of Concurrent Task
> --------------------------------------------------------
>
> Key: LUCENE-8989
> URL: https://issues.apache.org/jira/browse/LUCENE-8989
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Atri Sharma
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> As discussed in [https://github.com/apache/lucene-solr/pull/815,]
> IndexSearcher should handle the case when the executor rejects the execution
> of a task (unavailability of threads?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
