Thanks, I ran into the problem when I issued the commit command to the
SOLR search server.
-Original Message-
From: J.J. Larrea [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 13, 2007 2:29 PM
To: solr-user@lucene.apache.org
Subject: Re: NFS Stale handle in a distributed SOLR
Sometimes one has to make things work in the environment one is handed (e.g.
virtualized servers, ALL storage resources resident on a SAN and accessed via
NFS, read-only mounts on the deployment instances with only the production
indexers having write access). While I agree that fast local inde
The straightforward solution is to not put your indexes on NFS. It is
slow and it causes failures like this.
I'm serious about that. I've seen several different search engines
(not just Solr/Lucene) get very slow and unreliable when the indexes
were on NFS.
wunder
On 9/13/07 10:59 AM, "Kasi Sank
Hi All,
I have multiple SOLR instances in read only mode accessing index files
on a NFS partition, I run the indexing/updating of indexing from another
SOLR
Instance. When I run a commit command on the search servers to warm up
the searchers after update I get 'NFS stale handle' error message.
