nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <j...@apache.org>
Subject [jira] Updated: (NUTCH-308) Maximum search time limit
Date Thu, 22 Jun 2006 01:01:30 GMT
     [ http://issues.apache.org/jira/browse/NUTCH-308?page=all ]

Andrzej Bialecki  updated NUTCH-308:
------------------------------------

    Attachment: timeout.patch

> Maximum search time limit
> -------------------------
>
>          Key: NUTCH-308
>          URL: http://issues.apache.org/jira/browse/NUTCH-308
>      Project: Nutch
>         Type: Improvement

>   Components: searcher
>     Versions: 0.8-dev
>     Reporter: Andrzej Bialecki 
>      Fix For: 0.8-dev
>  Attachments: timeout.patch
>
> With large indexes it may often happen that search servers don't respond in time. The
IPC code time-outs such calls, and the front-end DistributedSearch.Client no longer expects
any results from the timed-out Server. However, the search thread is still running on the
Server, until it completes (which may be even tens of seconds later), consuming server resources.
Subsequent requests will run much slower, eventually leading to 100% CPU/disk utilization
and an avalanche of timeouts.
> 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 message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message