[
https://issues.apache.org/jira/browse/SOLR-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223135#comment-13223135
]
Eric Pugh commented on SOLR-2184:
---------------------------------
I recently ran into this same problem when I moved from 10 to 60+ shards. With
60+ shards, I would get back frequent connection errors from various shards.
Changing the default max connection per host to a larger number, like 2048
solved the problem. When debugging this, I saw that in Solr 4, the default
value is much larger. Here is a link to the commit:
http://svn.apache.org/viewvc/lucene/dev/trunk/solr/core/src/java/org/apache/solr/handler/component/HttpShardHandlerFactory.java?r1=1291530&r2=1292353&diff_format=h.
I don't know if this needs to be configurable, or just bumped up to a
larger number, like the 256 value from Solr 4.
> Allow configuration of max connections for shards
> -------------------------------------------------
>
> Key: SOLR-2184
> URL: https://issues.apache.org/jira/browse/SOLR-2184
> Project: Solr
> Issue Type: Improvement
> Reporter: patrick o'leary
> Attachments: SOLR-2184.patch, shard_request_hosts.patch
>
>
> Shard-ed requests are hard coded
> {code}
> mgr.getParams().setDefaultMaxConnectionsPerHost(20);
> mgr.getParams().setMaxTotalConnections(10000);
> {code}
> We should allow config parameters such as
> shard-max-conn-per-host, shard-max-total-conn
> To allow you to tune as needed.
--
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: [email protected]
For additional commands, e-mail: [email protected]
