[ https://issues.apache.org/jira/browse/SOLR-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660656#action_12660656 ]
Lance Norskog commented on SOLR-844: ------------------------------------ Concur with dubious reaction. However, what you mention about multiple hops is a valid point. The distributed searcher could have an option that returns the shard set. A Solr client library could run the distributed search/merge and return that to its calling app. A similar list of active "all-in-one" servers could also be handed back to this mythical client library. Anyway, here's a use case for load balancing: we wanted to take a server out of the load balancer, rewarm its caches, then put it back in the balancer. > A SolrServer impl to front-end multiple urls > -------------------------------------------- > > Key: SOLR-844 > URL: https://issues.apache.org/jira/browse/SOLR-844 > Project: Solr > Issue Type: New Feature > Components: clients - java > Affects Versions: 1.3 > Reporter: Noble Paul > Assignee: Shalin Shekhar Mangar > Fix For: 1.4 > > Attachments: SOLR-844.patch, SOLR-844.patch > > > Currently a {{CommonsHttpSolrServer}} can talk to only one server. This > demands that the user have a LoadBalancer or do the roundrobin on their own. > We must have a {{LBHttpSolrServer}} which must automatically do a > Loadbalancing between multiple hosts. This can be backed by the > {{CommonsHttpSolrServer}} > This can have the following other features > * Automatic failover > * Optionally take in a file /url containing the the urls of servers so that > the server list can be automatically updated by periodically loading the > config > * Support for adding removing servers during runtime > * Pluggable Loadbalancing mechanism. (round-robin, weighted round-robin, > random etc) > * Pluggable Failover mechanisms -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.