lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrzej Bialecki ...@getopt.org>
Subject Re: Adding lock timeouts to write.lock
Date Mon, 11 Aug 2003 20:30:38 GMT
Doug Cutting wrote:
> Scott Ganyo wrote:
> 
>> Thanks, Doug.  Unfortunately, as you know, IndexWriter isn't the only 
>> one using these locks:
>>
>> 1) IndexReader uses the "commit.lock" when opening.
>>
>> 2) IndexReader needs to create a "write.lock" during the delete process.
>>
>> So, although perhaps not a perfect solution, it seems to me that Lock 
>> is still at least a common place to define these and less confusing 
>> than putting them on IndexWriter -- which is only one of the classes 
>> that use then contants.
> 
> 
> Yes, I realize that multiple classes use these constants.  But they're 
> only used in the index package, so I thought they'd be better off there. 
>  They're not used by anything in the storage package.  IndexWriter uses 
> them the most, so it seems like the best place to me.

On a somewhat related note... The issue of creating locks (and having 
some central place to manage them) is related to read-only environment. 
I was trying the other day to come up with an easy solution for opening 
index in read-only mode. Short of rewriting FSDirectory I couldn't find 
any solution. Even this wasn't perfect, because some operations (like 
IndexReader.delete()) are cached, and don't report immediately that they 
will ultimately fail... Any ideas here?

-- 
Best regards,
Andrzej Bialecki

-------------------------------------------------
Software Architect, System Integration Specialist
CEN/ISSS EC Workshop, ECIMF project chair
EU FP6 E-Commerce Expert/Evaluator
-------------------------------------------------
FreeBSD developer (http://www.freebsd.org)




Mime
View raw message