My typical way of adding documents is through SolrJ, where I commit after every batch of documents (where the batch size is configurable)
I have now tried committing several times, from the command line (curl) with and without openSearcher=true. It does not affect anything. Dave -----Original Message----- From: Mark Miller [mailto:markrmil...@gmail.com] Sent: Friday, November 16, 2012 11:04 AM To: solr-user@lucene.apache.org Subject: Re: inconsistent number of results returned in solr cloud How did you do the final commit? Can you try a lone commit (with openSearcher=true) and see if that affects things? Trying to determine if this is a known issue or not. - Mark On Nov 16, 2012, at 1:34 PM, "Buttler, David" <buttl...@llnl.gov> wrote: > Hi all, > I buried an issue in my last post, so let me pop it up. > > I have a cluster with 10 collections on it. The first collection I loaded > works perfectly. But every subsequent collection returns an inconsistent > number of results for each query. The queries can be simply *:*, or more > complex facet queries. If I go to individual cores and issue the query, with > distrib=false, I get a consistent number of results. I am wondering if there > is some delay in returning results from my shards, and the queried node just > times out and displays the number of results that it has received so far. If > there is such a timeout, it must be very small, as my QTime is around 11 ms. > > Dave
