robert engels wrote:
Thanks.
So all writers still need to get the write lock, before opening the
reader in order to maintain transactional consistency.
I don't understand what you mean by "before opening the reader"? A
writer acquires the write.lock before opening. Readers do not,
unless/until they do their first write operation (deleteDocument/
setNorm).
Was there performance testing done on the lockless commits with
heavy contention? I would think that reading the directory to find
the latest segments file would be slower. Is there a 'latest
segments' file to avoid this? If not, there probably should be. As
long as the data fits in a single disk block (which is should), I
don't think you will have a consistency problem.
Performance tests were done (see LUCENE-710).
And, yes, there is a file segments.gen that records the latest
segment, but it is used along with the directory listing to find the
current segments file.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
