Set the parameter to false as per the documentation
Erick
On Jan 27, 2008 5:11 AM, anjana m <[EMAIL PROTECTED]> wrote:
> yes i dont want the old index to be deletd since its running on my app
> server..
> any suggestion..?
>
> On Jan 27, 2008 3:07 PM, Daniel Naber <[EMAIL PROTECTED]>
> wrote
I've seen this before.
When you have a ton of threads, any synchronization point can become a
bottleneck, regardless of how small the synchronized code is. If it
wasn't isDeleted, it would be something else.
The better strategy from an app standpoint is to throttle the number of threads.
-Yonik
Otis,
Thanks for the response.
All the threads are blocked in the same place. Here's the typical
stacktrace, I've remove the stuff outside of the lucene
libraries. I have about 100 threads blocked in the same place.
btpool0-5 [BLOCKED; waiting to lock
[EMAIL PROTECTED]
org.apache.lucene.index.Se
yes i dont want the old index to be deletd since its running on my app
server..
any suggestion..?
On Jan 27, 2008 3:07 PM, Daniel Naber <[EMAIL PROTECTED]> wrote:
> On Sonntag, 27. Januar 2008, anjana m wrote:
>
> > IndexWriter writer = new IndexWriter(indexDir, new
> > StandardAnalyzer()
On Sonntag, 27. Januar 2008, anjana m wrote:
> IndexWriter writer = new IndexWriter(indexDir, new
> StandardAnalyzer(), true);
The true parameter means that the old index will be deleted, is that your
problem?
Regards
Daniel
--
http://www.danielnaber.de
-
