Hmmm, nothing quite makes sense here.... Here are some experiments: 1> avoid the load balancer and issue queries like http://solr_server:8983/solr/collection/q=whatever&distrib=false
the &distrib=false bit will cause keep SolrCloud from trying to send the queries anywhere, they'll be served only from the node you address them to. that'll help check whether the nodes are consistent. You should be getting back the same results from each replica in a shard (i.e. 2 of your 6 machines). Next, try your failing query the same way. Next, try your failing query from a browser, pointing it at successive nodes. Where is the first place problems show up? My _guess_ is that your load balancer isn't quite doing what you think, or your cluster isn't set up the way you think it is, but those are guesses. Best, Erick On Thu, Oct 2, 2014 at 2:51 PM, S.L <simpleliving...@gmail.com> wrote: > Hi All, > > I am trying to query a 6 node Solr4.7 cluster with 3 shards and a > replication factor of 2 . > > I have fronted these 6 Solr nodes using a load balancer , what I notice is > that every time I do a search of the form > q=*:*&fq=(id:9e78c064-919f-4ef3-b236-dc66351b4acf) it gives me a result > only once in every 3 tries , telling me that the load balancer is > distributing the requests between the 3 shards and SolrCloud only returns a > result if the request goes to the core that as that id . > > However if I do a simple search like q=*:* , I consistently get the right > aggregated results back of all the documents across all the shards for > every request from the load balancer. Can someone please let me know what > this is symptomatic of ? > > Somehow Solr Cloud seems to be doing search query distribution and > aggregation for queries of type *:* only. > > Thanks.