OK then that's the problem. Unlike local file systems, NFS makes no effort to protect still-open-for-read files from being deleted (which Lucene by default relies on by default).
The solution is easy: create your own IndexDeletionPolicy to "protect" old index commit points from being deleted until all of the readers have switched to a new commit. The simplest approach is time based, ie, a commit is not deleted until it's more than X minutes/hours old, and then to ensure your readers reopen at a faster rate than that. Mike McCandless http://blog.mikemccandless.com On Mon, Jan 9, 2012 at 4:10 AM, superruiye <superru...@gmail.com> wrote: > yes，i use it to share index,and one server is master to writer and read;the > others are slaver,read only. > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Why-read-past-EOF-tp3639401p3644074.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
