[
https://issues.apache.org/jira/browse/SOLR-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646143#action_12646143
]
Ian Holsman commented on SOLR-844:
----------------------------------
your opening a can of worms in this one Noble.
Firstly there are about a thousand ways you can handle load balancing already
out there on the backend side (both hardware and software). you can achieve
what you want today by using the apache webserver and mod_proxy_balancer -
http://httpd.apache.org/docs/2.2/mod/mod_proxy_balancer.html
Secondly doing it on the client side means you will need to track ALL the
clients who use your service. I don't think the URL config thing won't work
well in practice.
Thirdly load balancing isn't easy. I've had the joy of debugging load balancing
errors and outages, and wouldn't want to have to go through that again
> 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.
