[
https://issues.apache.org/jira/browse/SOLR-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646165#action_12646165
]
Noble Paul commented on SOLR-844:
---------------------------------
bq.Firstly there are about a thousand ways you can handle load balancing
already out there on the backend side (both hardware and software)
Yes , But each extra layer introduces its own overhead. (in latency , hardware
and maintenance). Moreover we are introducing a single point of failure.
This is similar to a MySql driver providing a feature to connect to multiple
servers (maters/slaves) . it does round-robin at the driver side and provide
automatic failover.
http://dev.mysql.com/doc/refman/5.0/en/connector-j-reference-replication-connection.html
bq.Secondly doing it on the client side means you will need to track ALL the
clients who use your service
Let us discuss how best this can be handled. This is just an extension of what
we already have , (a thin wrapper).
> 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.
