[
https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552147
]
Michael McCandless commented on LUCENE-997:
-------------------------------------------
I think one benefit of a dedicated timer thread is not being affected
by clock shift on the machine. System.currentTimeMillis() is not
guaranteed to be monotonic. System.nanoTime() (1.5 only!) tries
to be (I think), but it's still not guaranteed.
Without a monotonic clock, if the clock shifts forward then it could
timeout in-flight queries (way) too early.
But: what happens when TimerThread overflows the int (a
2*1024*1024*1024)? Is it the caller's job to deal with the
wraparound?
> 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: LuceneTimeoutTest.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]
