You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Otis Gospodnetic (JIRA)" <ji...@apache.org> on 2009/01/22 22:13:59 UTC

[jira] Issue Comment Edited: (SOLR-844) A SolrServer impl to front-end multiple urls

    [ https://issues.apache.org/jira/browse/SOLR-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666296#action_12666296 ] 

otis edited comment on SOLR-844 at 1/22/09 1:12 PM:
----------------------------------------------------------------

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?


      was (Author: otis):
    I'm not sure there is a clear consensus about this functionality being a good thing.  Perhaps we can get more people's opinions?

  
> 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.


Re: [jira] Issue Comment Edited: (SOLR-844) A SolrServer impl to front-end multiple urls

Posted by Walter Underwood <wu...@netflix.com>.
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.

wunder

On 1/22/09 1:13 PM, "Otis Gospodnetic (JIRA)" <ji...@apache.org> wrote:

> 
>     [ 
> https://issues.apache.org/jira/browse/SOLR-844?page=com.atlassian.jira.plugin.
> system.issuetabpanels:comment-tabpanel&focusedCommentId=12666296#action_126662
> 96 ] 
> 
> otis edited comment on SOLR-844 at 1/22/09 1:12 PM:
> ----------------------------------------------------------------
> 
> 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?
> 
> 
>       was (Author: otis):
>     I'm not sure there is a clear consensus about this functionality being a
> good thing.  Perhaps we can get more people's opinions?
> 
>   
>> 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