Internal Lucene document IDs are signed 32 bit numbers, so having 2.5B docs seems to be just _asking_ for trouble. Which could explain the fact that this just came out of thin air. If you kept adding docs to the problem instance, you wouldn't have changed configs etc, just added more docs....
I really think it's time to shard. Best Erick On Wed, Jun 20, 2012 at 2:15 AM, avenka <ave...@gmail.com> wrote: > For the first install, I copied over all files in the directory "example" > into, let's call it, "install1". I did the same for "install2". The two > installs run on different ports, use different jar files, are not really > related to each other in any way as far as I can see. In particular, they > are not "multicore". They have the same access control setup via jetty. I > did a diff on config files and confirmed that only port numbers are > different. > > Both had been running fine in parallel importing from a common database for > several weeks. The documents indexed by install1, the problematic one > currently, is a vastly bigger (~2.5B) superset of those indexed by install2 > (~250M). > > At this point, select queries on install1 incurs the NullPointerException > irrespective of whether install2 is running or not. The log file looks like > it is indexing normally as always though. The index is also growing at the > usual rate each day. Just select queries fail. :( > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/solr-java-lang-NullPointerException-on-select-queries-tp3989974p3990476.html > Sent from the Solr - User mailing list archive at Nabble.com.
