Were there any exceptions inside Lucene, before the hang?
The fact that you're hitting AlreadyClosedException is a spooky sign
-- that means IW thinks you had in fact closed the writer, but then
used it again.
For increasing indexing throughput, I'd start here:
http://wiki.apache.org/lucene-
Hi Mike
There are other threads involved but none are simultaneously modifying
the index.
There is one thread that retrieves the total count every 2 seconds on
the index for GUI display:
public long getTotalMessageCount(Volume volume) throws
MessageSearchException {
if (volum
Hi Mike
There are other threads involved but none are simultaneously modifying
the idex.
There is one read that retrieves the total count every 2 seconds on the
Index for GUI display:
public long getTotalMessageCount(Volume volume) throws
MessageSearchException {
if (volume =
Are there other threads involved, besides the one hung in close? Can
you post their stack traces?
This stack trace seems to indicate that IW believes another thread is
in the process of closing.
Can you call IndexWriter.setInfoStream and post the output leading to the hang?
Mike
On Fri, Oct 9,
HI Michael / Uwe / others
Sorry for the repost... it just does not look like the earlier message I
sent go through.
FYI: there are no large Lucene merges taking place.
Jamie Band wrote:
Hi Michael
Thanks for your help. Here are the stacks:
index processor [TIME_WAITING] CPU time: 33:01
java
