lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jiangwen wei (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-3606) Set the default timeout of HttpClient to a nonzero value
Date Mon, 09 Jul 2012 07:45:33 GMT

     [ https://issues.apache.org/jira/browse/SOLR-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

jiangwen wei updated SOLR-3606:
-------------------------------

    Description: 
The default timeout of HttpClient in HttpShardHandlerFactory and SolrCmdDistributor is set
to zero.
Zero timeout means infinite timeout, which may cause infinite waiting.

Considering the following case which is observed in our solr cluster:
There are two servers A and B in solr cluster with two shards.
Server A receive a search request from client and send a sub request to server B.
Server B also receive a search request from client and send a sub request to server A.
the two requests cannot be completed forever, if the threads of jetty server in server A and
server B exhausted.

  was:
set timeout to zero means infinite timeout, which can cause infinite waiting.
considering the following case:
there are two servers A and B in solr cluster with two shards.
server A receive a search request from client and send a sub request to server B.
server B also receive a search request from client and send a sub request to server A.
the two requests cannot be completed forever, if the threads of jetty server in server A and
server B exhausted.

    
> Set the default timeout of HttpClient to a nonzero value
> --------------------------------------------------------
>
>                 Key: SOLR-3606
>                 URL: https://issues.apache.org/jira/browse/SOLR-3606
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 5.0
>            Reporter: jiangwen wei
>
> The default timeout of HttpClient in HttpShardHandlerFactory and SolrCmdDistributor is
set to zero.
> Zero timeout means infinite timeout, which may cause infinite waiting.
> Considering the following case which is observed in our solr cluster:
> There are two servers A and B in solr cluster with two shards.
> Server A receive a search request from client and send a sub request to server B.
> Server B also receive a search request from client and send a sub request to server A.
> the two requests cannot be completed forever, if the threads of jetty server in server
A and server B exhausted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message