Are you able to reproduce the corruption? If at any time you accidentally had two writers open on the same index, it could have created this corruption.
Writing to an index over NFS ought to be OK, however, it's not well tested. You should use SimpleFSLockFactory (not the default NativeFSLockFactory). The more "typical" way people use NFS is to write to an index on a local disk, and then other machines read from that index using NFS. In any event performance is usually much worse than using local disks ... Mike McCandless http://blog.mikemccandless.com On Thu, Nov 1, 2012 at 10:32 PM, superruiye <superru...@gmail.com> wrote: > oh ,thx,I don't know CheckIndex before...and I use to fix my error index,it > is OK... > I use NFS to share my index,and no change to the LogFactory. > How could I avoid this problem,and not only fix after it was broken > suddenly? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/read-past-EOF-when-merge-tp4017179p4017734.html > Sent from the Lucene - Java Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
