Right, if you optimize, at the end maxDocs should == numDocs. Usually the document reclamation stuff is done when segments merge, but that won't happen in this case since this index is becoming static, so a manual optimize is probably indicated.
Something like this should also work, either way: http://localhost:8983/solr/update?stream.body=<optimize/> But be prepared to wait for a very long time..... I'd copy it somewhere else first just for safety's sake.... Best Erick On Thu, Jun 21, 2012 at 12:52 PM, avenka <ave...@gmail.com> wrote: > Erick, much thanks for detailing these options. I am currently trying the > second one as that seems a little easier and quicker to me. > > I successfully deleted documents with IDs after the problem time that I do > know to an accuracy of a couple hours. Now, the stats are: > numDocs : 2132454075 > maxDoc : -2130733352 > The former is nicely below 2^31. But I can't seem to get the latter to > "decrease" and become positive by deleting further. > > Should I just run an optimize at this point? I have never manually run an > optimize and plan to just hit > http://<machine_name>/solr/update?optimize=true > Can you confirm this? > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/solr-java-lang-NullPointerException-on-select-queries-tp3989974p3990798.html > Sent from the Solr - User mailing list archive at Nabble.com.
