2010/6/25 Ya-Wen Hsu <y...@eline.com>
> This situation doesn't happen consistently. When we only ran the
> problematic core, the indexing took significant longer than usual(4hrs -> 11
> hrs). It ran successful in the end. When we ran indexing for all cores at
> the same time, the problematic core never finished indexing such that we
> have to kill the process. This happened twice already. I'm running it
> parallel again to see if the problem still persists.
>
Off the top of my head:
Have you accidentally opened this core multiple times within the same JVM?
I had the same thing happen to me when I was testing out a Solr interface I
had written under JRuby; that was loads of fun to track down...
How physically large is the core ('du -sh' if you're on Unix), and how many
files does the index contain? I've run into issues where frequent updates
created a lot of index files, and which slowed down all core access.
If you've got a lot of index files, has the problem core been optimized?
