[
https://issues.apache.org/jira/browse/SOLR-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409368#comment-13409368
]
Yonik Seeley commented on SOLR-3606:
------------------------------------
A 10 second timeout is too short for some of the types of requests that may be
run. The problem with setting any timeout is that we don't know the upper
bound.
Large commits or optimizes esp could take a very long time.
The example server is configured for up to 10K threads to avoid running out.
> 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
> Attachments: SOLR-3606.patch
>
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
