[
https://issues.apache.org/jira/browse/SOLR-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659365#comment-13659365
]
philip hoy commented on SOLR-4823:
----------------------------------
The load balancer does indeed use round robin to pick a shard replica to
forward the request on to. However it does not do the clever stuff to pick out
what shards are possible candidates for a particular query. That role is
fulfilled by the org.apache.solr.handler.component.HttpShardHandler.
> Split LBHttpSolrServer into two classes one for the solrj use case and one
> for the solr cloud use case
> ------------------------------------------------------------------------------------------------------
>
> Key: SOLR-4823
> URL: https://issues.apache.org/jira/browse/SOLR-4823
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: philip hoy
> Priority: Minor
>
> The LBHttpSolrServer has too many responsibilities. It could perhaps be
> broken into two classes, one in solrj to be used in the place of an external
> load balancer that balances across a known set of solr servers defined at
> construction time and one in solr core to be used by the solr cloud
> components that balances across servers dependant on the request.
> To save code duplication, if much arises an abstract bass class could be
> introduced in to solrj.
--
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]
