ple threads sharing a writer for
> performance reasons.
>
> Michael
>
> -Original Message-
> From: Li Bing [mailto:lbl...@gmail.com]
> Sent: Thursday, October 29, 2009 8:02 PM
> To: Michael Garski
> Cc: lucene-net-user@incubator.apache.org
> Subject: Re: Exce
arski
Cc: lucene-net-user@incubator.apache.org
Subject: Re: Exceptions When Indexing with Multi-threading
Dear Michael,
Yes, each thread in my system has its own IndexWriter. But all of them
are synchronized by a unique lock. So I think the exception should not
occur, right? If the threads sh
Bing [mailto:lbl...@gmail.com]
> Sent: Wednesday, October 28, 2009 10:57 PM
> To: lucene-net-user@incubator.apache.org
> Cc: Li Bing - Gmail
> Subject: Exceptions When Indexing with Multi-threading
>
> Dear all,
>
> Today I got exceptions when indexing with multi-threadin
exing with Multi-threading
Dear all,
Today I got exceptions when indexing with multi-threading. It says
that "deletable.new" or "segments.new" are accessed by other
processes. So it cannot rename ...
However, I have used "ReaderWriterSlim" lock to avoid the relevant
exing with Multi-threading
Dear all,
Today I got exceptions when indexing with multi-threading. It says
that "deletable.new" or "segments.new" are accessed by other
processes. So it cannot rename ...
However, I have used "ReaderWriterSlim" lock to avoid the relevant
fo
Dear all,
Today I got exceptions when indexing with multi-threading. It says
that "deletable.new" or "segments.new" are accessed by other
processes. So it cannot rename ...
However, I have used "ReaderWriterSlim" lock to avoid the relevant
folders to be accessed b
