[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12555205
]
Timo Nentwig commented on LUCENE-997:
-------------------------------------
True, unfortunately, but still better than nothing (->current situation). This
approach isn't very precise in matters of timing either. Also, throwing a
RuntimeException feels more like a hack than well thought out code...
I don't know Lucene's code good enough in order to estimate whether it's
possible to build a real timeout machanism at all/without changing the
API/rewriting a lot of code but it's incredibly important to be able to cancel
running queries. You don't want to servers under high load suffering from
lucene queries running up to multiple *minutes* at the same time consuming
quite a lot of memory. And it makes no sense either because nobody is waiting
so long for results...
> Add search timeout support to Lucene
> ------------------------------------
>
> Key: LUCENE-997
> URL: https://issues.apache.org/jira/browse/LUCENE-997
> Project: Lucene - Java
> Issue Type: New Feature
> Reporter: Sean Timm
> Priority: Minor
> Attachments: HitCollectorTimeoutDecorator.java,
> LuceneTimeoutTest.java, MyHitCollector.java, timeout.patch, timeout.patch
>
>
> This patch is based on Nutch-308.
> This patch adds support for a maximum search time limit. After this time is
> exceeded, the search thread is stopped, partial results (if any) are returned
> and the total number of results is estimated.
> This patch tries to minimize the overhead related to time-keeping by using a
> version of safe unsynchronized timer.
> This was also discussed in an e-mail thread.
> http://www.nabble.com/search-timeout-tf3410206.html#a9501029
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
