Not quite sure what's happening here. It would be interesting to see whether the requests are actually going to the right IP, by tailing out the logs.
It _may_ be that the &distrib=false isn't honored if there is no core on the target machine (I haven't looked at the code). To test that, go ahead and tail out the log on ip1 (in your first scenario) and then send the query to ip2. Actually, I'm asking you to do an experiment for me <G>... distrib=false _may_ just be going to the first core specified that can be found..... Best Erick On Fri, Jul 26, 2013 at 3:41 AM, vicky desai <vicky.de...@germinait.com> wrote: > Hi Erick, > > First Of all sorry for the late reply. > > The scenario is as follows > 1. Create a solr set up on two machines say (ip1 and ip2) with shard=1 and > external zoo-keeper > 2. Now if i create a core x on machine with ip1 only and use the query > http://ip1:port1/solr/x/select?q=*:*&distrib=false > http://ip2:port2/solr/x/select?q=*:*&distrib=false > > I get the same result that is docs are visible. However practically the core > is not on instance with ip2 so i was expecting that query to fail > > 3. Now if I create the core on machine 2 as well and then hit those two > queries second query gives me response 0 untill it comes in sync with ip1. > This behavious is as expected. > > Please correct me if my expections are wrong and thanks for all the help > provided untill now > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Querying-a-specific-core-in-solr-cloud-tp4079964p4080528.html > Sent from the Solr - User mailing list archive at Nabble.com.
