You'll certainly need to factor in the performance of NFS versus local disks.
My experience is that smallish low activity indexes work just fine on NFS, but large high activity indexes are not so good, particularly if you have a lot of modifications to the index. You may want to install a custom IndexDeletionPolicy. See the javadocs for details with specific reference to NFS. -- Ian. On Tue, Oct 2, 2012 at 3:21 AM, Vitaly Funstein <vfunst...@gmail.com> wrote: > How tolerant is your project of decreased search and indexing performance? > You could probably write a simple test that compares search and write > speeds of local and NFS-mounted indexes and make the decision based on the > results. > > On Mon, Oct 1, 2012 at 3:06 PM, Jong Kim <jong.luc...@gmail.com> wrote: > >> Hi, >> >> According to the Lucene In Action (Second Edition), the section 2.11.2 >> "Accessing an index over a remote file system" explains that there are >> issues related to accessing a Lucene index across remote file system >> including NFS. >> >> I'm particuarly interested in NFS compatibility, and wondering if there has >> been any work done to solve or mitigate this problem. Has this issue been >> addressed? If not, are there some reliable work-arounds that make this >> possible at the expense of some sacrifice in other areas? >> >> Any information would be greatly appreciated, since my project heavily >> depends on the feasibility of this. >> >> Thanks >> /Jong >> --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
