Apache
/
lucene
mirror of https://github.com/apache/lucene.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Document-only fix for SOLR-4404 hopefully clarifying that it's OK to use LBHttpSolrServer in SolrCloud mode 

git-svn-id: https://svn.apache.org/repos/asf/lucene/dev/trunk@1444316 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Erick Erickson 2013-02-09 02:38:00 +00:00
parent 6677bbf60f
commit 1f7f80c697
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
solr/solrj/src/java/org/apache/solr/client/solrj/impl/LBHttpSolrServer.java
View File

@ -37,8 +37,16 @@ import java.util.*;
/** /**
* LBHttpSolrServer or "LoadBalanced HttpSolrServer" is a load balancing wrapper around * LBHttpSolrServer or "LoadBalanced HttpSolrServer" is a load balancing wrapper around
* {@link org.apache.solr.client.solrj.impl.HttpSolrServer}. This is useful when you * {@link org.apache.solr.client.solrj.impl.HttpSolrServer}. This is useful when you
* have multiple SolrServers and the requests need to be Load Balanced among them. This should <b>NOT</b> be used for * have multiple SolrServers and the requests need to be Load Balanced among them.
* indexing. Also see the <a href="http://wiki.apache.org/solr/LBHttpSolrServer">wiki</a> page. *
* Do <b>NOT</b> use this class for indexing in master/slave scenarios since documents must be sent to the
* correct master; no inter-node routing is done.
*
* In SolrCloud (leader/replica) scenarios, this class may be used for updates since updates will be forwarded
* to the appropriate leader.
*
* Also see the <a href="http://wiki.apache.org/solr/LBHttpSolrServer">wiki</a> page.
*
* <p/> * <p/>
* It offers automatic failover when a server goes down and it detects when the server comes back up. * It offers automatic failover when a server goes down and it detects when the server comes back up.
* <p/> * <p/>
@ -46,7 +54,7 @@ import java.util.*;
* <p/> * <p/>
* If a request to a server fails by an IOException due to a connection timeout or read timeout then the host is taken * If a request to a server fails by an IOException due to a connection timeout or read timeout then the host is taken
* off the list of live servers and moved to a 'dead server list' and the request is resent to the next live server. * off the list of live servers and moved to a 'dead server list' and the request is resent to the next live server.
* This process is continued till it tries all the live servers. If atleast one server is alive, the request succeeds, * This process is continued till it tries all the live servers. If at least one server is alive, the request succeeds,
* and if not it fails. * and if not it fails.
* <blockquote><pre> * <blockquote><pre>
* SolrServer lbHttpSolrServer = new LBHttpSolrServer("http://host1:8080/solr/","http://host2:8080/solr","http://host2:8080/solr"); * SolrServer lbHttpSolrServer = new LBHttpSolrServer("http://host1:8080/solr/","http://host2:8080/solr","http://host2:8080/solr");