[
https://issues.apache.org/jira/browse/LUCENE-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531309
]
Michael McCandless commented on LUCENE-1011:
--------------------------------------------
Once I got through the locking issue (switched Patrick's test to use
SimpleFSLockFactory), I could no longer reproduce his issue, but he
could in his environment. So I worked out a simple change to how the
segments_N file is located: instead of first trying the directory
listing and then second falling back to reading segments.gen, always
try both and then use whichever generation is larger. This way we can
tolerate a stale directory cache, or a stale file contents cache
(though not both at the same time). In Patrick's testing this looks
to have resolved the issue.
I also fixed IndexFileDeleter to try specifically loading the current
commit point if this point was not seen in the directory listing
(which would happen if directory listing cache was stale), and,
improved messaging in IndexWriter (when you call setInfoStream(...))
to print more details about the configuration of the writer, to aid in
future remote debugging.
> Two or more writers over NFS can cause index corruption
> -------------------------------------------------------
>
> Key: LUCENE-1011
> URL: https://issues.apache.org/jira/browse/LUCENE-1011
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Affects Versions: 1.9, 2.0.0, 2.0.1, 2.1, 2.2, 2.3, 2.4, 2.9
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 2.3
>
> Attachments: LUCENE-1011.patch
>
>
> When an index is used over NFS, and, more than one machine can be a
> writer such that they swap roles quickly, it's possible for the index
> to become corrupt if the NFS client directory cache is stale.
> Not all NFS clients will show this. Very recent versions of Linux's
> NFS client do not seem to show the issue, yet, slightly older ones do,
> and the latest Mac OS X one does as well.
> I've been working with Patrick Kimber, who provided a standalone test
> showing the problem (thank you Patrick!). This came out of this
> thread:
>
> http://www.gossamer-threads.com/lists/engine?do=post_view_flat;post=50680;page=1;sb=post_latest_reply;so=ASC;mh=25;list=lucene
> Note that the first issue in that discussion has been resolved
> (LUCENE-948). This is a new issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
