[ 
https://issues.apache.org/jira/browse/SOLR-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649378#comment-13649378
 ] 

Shawn Heisey commented on SOLR-4448:
------------------------------------

[~rjernst] first let me say that I am having this discussion because what 
you're saying goes against my limited understanding, and by stating what I 
think and listening to your response, I might learn something.  You probably 
already know the things that I am saying.  I might even find that I 
misunderstood what you were saying and that I agree with you.

bq. Load balancing is used by distributed search. It happens to also be used 
for uploading documents, which is a client feature. Clients shouldn't be using 
this for sending distributed search requests. Solr does that.

I've just done a non-detailed review of CloudSolrServer.  It uses a new 
LBHttpSolrServer object with a customized URL list for every request.  Queries 
get sent to all replicas, updates only get sent to leaders.  A TODO says that 
currently there is no support in the object for sending updates to the correct 
leader based on a hashing algorithm.

Outside of SolrCloud, the LB object makes sense for clients in master-slave 
replication environments, but only on the query side.  Updates have to be 
directed to the master only.  A separate load balancer does give you more 
flexibility, but not everyone wants to invest the time (or possibly money) 
required.

If the client on the server side and the client on the client side need 
identical functionality, then the existing situation makes sense -- one 
implementation in the org.apache.solr.client.solrj namespace.  If we think 
they'll ever diverge, even a little bit, then having an abstract class in the 
org.apache.solr.common namespace makes sense, although it should still be in 
the solrj source tree.

                
> Allow the solr internal load balancer to be more easily pluggable.
> ------------------------------------------------------------------
>
>                 Key: SOLR-4448
>                 URL: https://issues.apache.org/jira/browse/SOLR-4448
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>            Reporter: philip hoy
>            Priority: Minor
>         Attachments: SOLR-4448.patch, SOLR-4448.patch
>
>
> Widen some access level modifiers to allow the load balancer to be extended 
> and plugged into an HttpShardHandler instance using an extended 
> HttpShardHandlerFactory.

--
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]

Reply via email to