[ https://issues.apache.org/jira/browse/SOLR-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582805#comment-13582805 ]
Raintung Li commented on SOLR-4449: ----------------------------------- Hi Philip, although all threads are in the ThreadPool that don't create the new thread, it still occupy the thread in the threads pool. For one search request, you will use double threads than before in the first request(Normal case). If it is coming 100 request, that means 300 threads will be used additional for 3 shards. If wait the response and send the second request in the HttpShardHandler.submit method, it will reduce the unnecessary threads cost. > Enable backup requests for the internal solr load balancer > ---------------------------------------------------------- > > Key: SOLR-4449 > URL: https://issues.apache.org/jira/browse/SOLR-4449 > Project: Solr > Issue Type: New Feature > Components: SolrCloud > Reporter: philip hoy > Priority: Minor > Attachments: SOLR-4449.patch > > > Add the ability to configure the built-in solr load balancer such that it > submits a backup request to the next server in the list if the initial > request takes too long. Employing such an algorithm could improve the latency > of the 9xth percentile albeit at the expense of increasing overall load due > to additional requests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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