if (doFlush)
flush(true, false);
} catch (OutOfMemoryError oom) {
hitOOM = true;
throw oom;
}
}
-Original Message-
From: Michael McCandless [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 30, 2008 2:45 AM
To: java-dev@lucene.apache.org
Subject: Re: Deadlock when m
ichael McCandless [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 30, 2008 2:45 AM
To: java-dev@lucene.apache.org
Subject: Re: Deadlock when multi-threading DocumentsWriter
The lock acquire order for all call stacks that lock on these two
classes should be IndexWriter then DocumentsWri
Jagadesh Nomula [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 29, 2008 2:43 PM
To: java-dev@lucene.apache.org
Subject: RE: Deadlock when multi-threading DocumentsWriter
Hi Mike,
Thanks for the comments.
Diagnosing, the stack trace the following statements, might run into
a nested lock.
e.org
Subject: Re: Deadlock when multi-threading DocumentsWriter
Can you post a patch with your full changes to DocumentsWriter and
IndexWriter?
That first thread is trying to flush, but is waiting for all threads
to leave DocumentsWriter (finish adding docs). The 2nd thread looks
like
e run into deadlock ?. This is not happening, so I should be
missing something. Any Comments ?
Thanks,
Jagdish
-Original Message-
From: Michael McCandless [mailto:[EMAIL PROTECTED]
Sent: Monday, July 28, 2008 4:33 PM
To: java-dev@lucene.apache.org
Subject: Re: Deadlock when
Can you post a patch with your full changes to DocumentsWriter and
IndexWriter?
That first thread is trying to flush, but is waiting for all threads
to leave DocumentsWriter (finish adding docs). The 2nd thread looks
like it's waiting for the flush to finish before proceeding. Are
the
