[
https://issues.apache.org/jira/browse/SOLR-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646463#action_12646463
]
Noble Paul commented on SOLR-844:
---------------------------------
no probs.
I'm sure that we do not use that internally , but there may be users who would
find it useful. (one man's meat is another man's poison)
Another use case is distributed search. Do we really want to have an extra hop
(Loadbalancer) for a shard to communicate to other shards? That is a few dozen
requests per client request . How many LoadBalancers would we need to handle
such load?
Is it big enough to merit a contrib package for itself?. Maybe.
> 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
> Fix For: 1.4
>
>
> 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 {{MultiCommonsHttpSolrServer}} which must automatically do a
> round-robin 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
