[
https://issues.apache.org/jira/browse/SOLR-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666409#action_12666409
]
shalinmangar edited comment on SOLR-844 at 1/22/09 7:46 PM:
---------------------------------------------------------------------
Walter Underwood on solr-dev:
bq. This would be useful if there was search-specific balancing, like always
send the same query back to the same server. That can make your cache far more
effective.
That is an interesting thought. Right now Solrj does not have the means to
construct the Query/Filter objects which are used as the key for the Solr
caches. Let us try to figure out if/how it can be implemented.
bq. I'm not sure there is a clear consensus about this functionality being a
good thing (also 0 votes). Perhaps we can get more people's opinions?
Yes Otis. That is exactly what I wanted to do with my comment :)
I guess most people think that this is a solved problem and I agree. Solr has
always required users to have load balancers and I guess our users have come to
accept it. But if you look at the new distributed systems being developed
(Katta/Bailey/CouchDB/Voldemort, etc.), almost none of them assume an external
load balancer or fail over system in their design. If they do, external systems
are made optional (Voldemort). Right now we force people to use and maintain an
external system if they have a Solr master/slave architecture. Apache and
mod_proxy_balancer are great but have a higher latency than hardware based load
balancers and these are not cheap.
The current patch is very simple. However, better ways to handle configuration
and load balancing can be added. I think this can be a good starting point for
the Solr 2.0 proposals. Unfortunately, very few of us have time to implement
all of the proposals in a big bang way. But if we focus on one issue at a time,
we will get somewhere close sooner. This might not be the code which ends up in
Solr 2.0 but I think it can provide a good transition path.
Thoughts?
was (Author: shalinmangar):
Walter Underwood on solr-dev:
bq. This would be useful if there was search-specific balancing,
like always send the same query back to the same server. That
can make your cache far more effective.
That is an interesting thought. Right now Solrj does not have the means to
construct the Query/Filter objects which are used as the key for the Solr
caches. Let us try to figure out if/how it can be implemented.
bq. I'm not sure there is a clear consensus about this functionality being a
good thing (also 0 votes). Perhaps we can get more people's opinions?
Yes Otis. That is exactly what I wanted to do with my comment :)
I guess most people think that this is a solved problem and I agree. Solr has
always required users to have load balancers and I guess our users have come to
accept it. But if you look at the new distributed systems being developed
(Katta/Bailey/CouchDB/Voldemort, etc.), almost none of them assume an external
load balancer or fail over system in their design. If they do, external systems
are made optional (Voldemort). Right now we force people to use and maintain an
external system if they have a Solr master/slave architecture. Apache and
mod_proxy_balancer are great but have a higher latency than hardware based load
balancers and these are not cheap.
The current patch is very simple. However, better ways to handle configuration
and load balancing can be added. I think this can be a good starting point for
the Solr 2.0 proposals. Unfortunately, very few of us have time to implement
all of the proposals in a big bang way. But if we focus on one issue at a time,
we will get somewhere close sooner. This might not be the code which ends up in
Solr 2.0 but I think it can provide a good transition path.
Thoughts?
> 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, 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.
