Re: lucene locking

2010-12-16 Thread Earl Hood
On Thu, Dec 16, 2010 at 8:36 AM, Donld Hill wrote: > Can I safely upgrade to a newer version, do I need to perform any updates on > the actual indices? >From my personal experience, upgrading from v2 to v3 required rebuilds of indices since we experienced some problems performing queries against

Re: lucene locking

2010-12-16 Thread Donld Hill
So will updating to a newer version of Lucene help with the performance when loading DOCS. I will also do some research to see what is being loaded as this is a 3rd party that's using Lucene. Can I safely upgrade to a newer version, do I need to perform any updates on the actual indices? On

Re: lucene locking

2010-12-16 Thread Doron Cohen
> > > I have a app that seems to be locking on some search calls. I am > including > > the stacktrace for the blocked and blocker thread. > Is it daedlock for sure? No search deadlock fixes were done since 2.1.0, so perhaps it is something else... > "TP-Processor177" daemon prio=10 tid=0x00

RE: lucene locking

2010-12-16 Thread Uwe Schindler
December 16, 2010 5:06 AM > To: java-user@lucene.apache.org > Subject: lucene locking > > I have a app that seems to be locking on some search calls. I am including > the stacktrace for the blocked and blocker thread. We are using the following > jars lucene-snowball-2.1.0.jar

lucene locking

2010-12-15 Thread Donld Hill
I have a app that seems to be locking on some search calls. I am including the stacktrace for the blocked and blocker thread. We are using the following jars lucene-snowball-2.1.0.jar and lucene-2.1.0.jar. The indexes are located on the local disk. We are running on multiple JVM's against the