[
https://issues.apache.org/jira/browse/SOLR-10697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246785#comment-16246785
]
Erick Erickson commented on SOLR-10697:
---------------------------------------
Why don't we have these all listed in the solr.xml file, along with, perhaps,
appropriate comments?
socketTimeout
connTimeout
maxConnectionsPerHost
maxConnections
retry
allowCompression
followRedirects
httpBasicAuthUser
httpBasicAuthPassword
Well, I'm not totally sure about the BasicAuth stuff, or maybe
allowCompression. But maxConnectionsPerHost and maybe maxConnections have
tripped up more than one person, having it in solr.xml might make it easier to
find/fix.
> Improve defaults for maxConnectionsPerHost
> ------------------------------------------
>
> Key: SOLR-10697
> URL: https://issues.apache.org/jira/browse/SOLR-10697
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Varun Thacker
> Assignee: Varun Thacker
> Priority: Minor
>
> Twice recently I've increased
> {{HttpShardHandlerFactory#maxConnectionsPerHost}} at a client and it helped
> improve query latencies a lot.
> Should we increase the default to say 100 ?
--
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
