lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Omar Didi" <od...@Cyveillance.com>
Subject RE: index merging
Date Wed, 15 Feb 2006 17:59:10 GMT
I have tried to use the isCurrent() method IndexReader to figure out if  an index is merging.
but since I have to do this evrytime I need to add a document, the performance got soooo slow.

here is what I am doing, I create 4 indexs and I am running with 4 threads. I do a round robbin
on the indexes when ever I process a new document. before adding a document I need to check
if the index is merging, if it's the case then send this document to an index that is not
merging.


is there a better to index with multi threads? or what is the fastet way to check that a index
is not merging?

thanks for any hints,

- Omar

-----Original Message-----
From: Yonik Seeley [mailto:yseeley@gmail.com]
Sent: Monday, February 06, 2006 10:03 AM
To: java-user@lucene.apache.org
Subject: Re: index merging


On 2/6/06, Vanlerberghe, Luc <Luc.Vanlerberghe@bvdep.com> wrote:
> Sorry to contradict you Yonik, but I'm pretty sure the commit lock is
> *not* locked during a merge, only while the "segments" file is being
> updated.

Oops, you're right.  Good thing too... if the commit lock was held
during merges, one couldn't even open up a new IndexReader.

-Yonik

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message