[ https://issues.apache.org/jira/browse/SOLR-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cassandra Targett resolved SOLR-3606. ------------------------------------- Resolution: Won't Fix I think based on Yonik's old comment and the lack of alternate ideas in the past 5+ years, this won't be changed. > 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: 6.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 was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org