We ran into a problem when implementing a similar infrastructure using NFS. We were updating our indexes continuously throughout the day which caused disk space problems when using NFS. I no longer recall the specific details, but in our configuration, NFS did not appear to flush stale file handles which then consumed disk space. Your configuration is different enough, esp. w/ updates planned for a specific time frame, that NFS might be a good solution.
It may also be worth taking a close look at Solr. They provide for index replication via rsync. We are in the process of moving from a custom Lucene application to a Solr based search application and are extremely pleased with progress thus far. -Mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tue 5/2/06 12:09 PM To: lucene-user@jakarta.apache.org Cc: Subject: Does lucene works with NFS? Hello: We are developing a WebSphere application using Lucene. Can we use the following architecture? 1. Store the index in a NFS file system which mount to all four UNIX machines 2. The WebSphere application just perform search (read only access to the index on NFS). 3. One of the four machines has a cron job that run every night to update the index on the NFS. Is this articture safe? The alternative is copy the index on all 4 machines. Then each machine also need a cron job to run every night to update the index. Which architecture do you recomend? Ningjun Wang Consulting Software Engineer LexisNexis
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
