[
https://issues.apache.org/jira/browse/SOLR-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582304#comment-13582304
]
philip hoy commented on SOLR-4449:
----------------------------------
Hi Raintung, I don't think there will be that many threads created, although it
depends somewhat on how the injected ThreadPoolExecuter and HttpClient are
configured.
For the good case, where the first shard responds within the delay period,
there is I think one thread for the orchestration code and one to send and
receive the request.
For the bad case, where there are three shards all responding slowly and where
the maximumConcurrentRequests is set to 3 or higher then it will again use one
thread for the the orchestration code but this time there will be three threads
used to send and receive responses for the three requests.
> 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: [email protected]
For additional commands, e-mail: [email protected]
