I can see what you mean, what you are expecting is a single host:port combination for "The Cloud" that always works, and you can call from your UI. That is perfectly possible, but its really not within the scope of Solr itself.
What you should understand is that Solr provides is a cloud that has fail-over and fault tolerance within itself. It provides the SolrJ client to access it, but if you want an HTTP interface to "Solr Cloud", that's a standard haproxy/load balancer setup. That can be done in hardware or software, there are guides galore on the web if you search for HAProxy. On 27 February 2014 11:41, Vineet Mishra <clearmido...@gmail.com> wrote: > Hi Per > > Thanks for your response, got it working. > But moreover I was more interested in querying the same Cloud from UI in a > case of one of the server down and querying the same server to get > collection result. But I guess thats not possible. > Thanks! > > > > > On Mon, Feb 24, 2014 at 7:36 PM, Per Steffensen <st...@designware.dk> > wrote: > > > On 24/02/14 13:04, Vineet Mishra wrote: > > > >> Can you brief as how to make a direct call to Zookeeper instead of Cloud > >> Collection(as currently I was querying the Cloud something like > >> *"http://192.168.2.183:8900/solr/collection1/select?q=*:* > >> <http://192.168.2.183:8900/solr/collection1/select?q=*:*>"* ) from UI, > >> now > >> > >> if I assume shard 8900 is down then how can I still make the call. > >> > > It is obvious that you cannot make the call to localhost:8900 - the > server > > listening to that port is down. You can make the call to any of the other > > servers, though. Information about which Solr-servers are running is > > available in ZooKeeper, CloudSolrServer reads that information in order > to > > know which servers to route requests to. As long as localhost:8900 is > down > > it will not route requests to that server. > > > > You do not make a "direct call to ZooKeeper". ZooKeeper is not an HTTP > > server that will receive your calls. It just has information about which > > Solr-servers are up and running. CloudSolrServers takes advantage of that > > information. You really cannot do without CloudSolrServer (or at least > > LBHttpSolrServer), unless you write a component that can do the same > thing > > in some other language (if the reason you do not want to use > > CloudSolrServer, is that your client is not java). Else you need to do > > other clever stuff, like e.g. what Shalin suggests. > > > > Regards, Per Steffensen > > >
