You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@nutch.apache.org by "Sami Siren (JIRA)" <ji...@apache.org> on 2005/04/04 20:45:20 UTC

[jira] Resolved: (NUTCH-15) ipc client timeout should be configurable

     [ http://issues.apache.org/jira/browse/NUTCH-15?page=history ]
     
Sami Siren resolved NUTCH-15:
-----------------------------

    Resolution: Fixed

I applied this, but changed the default timeout to 10000 msecs in nutch-default.xml

> ipc client timeout should be configurable
> -----------------------------------------
>
>          Key: NUTCH-15
>          URL: http://issues.apache.org/jira/browse/NUTCH-15
>      Project: Nutch
>         Type: Improvement
>   Components: searcher
>     Reporter: Stefan Grroschupf
>     Priority: Blocker
>  Attachments: timeOutPatch.txt
>
> The timeout of the ipc client is hard coded to 10 seconds. 
> Under heavy load it is common that for example that search servers crashs, since they are just overloaded.
> In  case just one search server crahs  every query took 10 seconds since in any case we wait for the crashed server.
> To make the timeout configurable would be a fist step, however we may can discuss implement a client / server similar to the dfs where the client is announcing itself to the server and the server add dynamically new clients or remove clients that fails for a given time period.
> This would be more confortable for production secarios since crashes are more oftern under heavy load and in case more server are involved.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira