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

Hoss Man commented on SOLR-844:
-------------------------------

bq. A wiki page is added here: http://wiki.apache.org/solr/LBHttpSolrServer

Actually i was referring to a need for javadoc comments in the class since 
there are none in the current patch. 

the wiki and/or static pages like hte tutorial make sense for features all 
users need to be aware of, but when we're talking about solrj code that java 
apps will explicitly compile against there isreally no substitute for good 
package, class, and method level javadocs.

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

Reply via email to