On 2/24/09 4:05 AM, Michael McCandless wrote:
I believe we still need this, for remote filesystems (like NFS) that
have inconsistent client-side caching.
The fsync() ensures the local IO system has moved the bytes/file
metadata to stable storage, but I'd expect remote caches would still
potentially be stale.
We could have an expert API to turn using the .gen file on/off? And then
default it to off in 3.0.
I think the .gen file and the CompoundFileWriter are the only places
left where we overwrite (parts of) files? To change the latter we could
move the cfs header to the segments file.
-Michael
Mike
Michael Busch wrote:
Hi,
with LUCENE-1044 we sync the FS after writing files. Do we still need
the segments.gen file to handle stale caches correctly?
-Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
