Hi There
Our app spends alot of time waiting for Lucene to finish writing to the
index. I'd like to minimize this. If you have a moment to spare, please
let me know if my LuceneIndex class presented below can be improved upon.
It is used in the following way:
luceneIndex = new
LuceneIndex(C
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 =
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
Incidentally, there are no Lucene merge threads doing any work. See
attached.
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
erver
was shutdown incorrectly. automatically deleting lock file.");
logger.warn("indexer is configured to deal with only
one indexer process.");
logger.warn("if you are running more than one
indexer, your index could be subject to corruption.&qu
Hi All
I have a long running situation where our indexing thread is getting
stuck indefinitely in IndexWriter's close method. Yourkit shows the
thread to be stuck in TIME_WAITING. Any idea's on what could be causing
this?
Could it be one of the streams or readers we passed to the document?
I
