Uh, avoid NFS and Lucene/Solr, unless you really really don't care about performance. We recently benchmarked Lucene indexing+searching+... on 1) local disk, 2) SAN, and 3) NFS.
You have the right to a single guess - which of the three was the slooooweeeeeesssst? Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- From: Kasi Sankaralingam <[EMAIL PROTECTED]> To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org> Sent: Tuesday, November 13, 2007 6:48:03 PM Subject: RE: two solr instances - index and commit This works, the only thing you need to be aware of is the NFS problem if you are running in a distributed environment sharing a NFS partition. a) Index and commit on instance (Typically partitioned as an index server) b) Issue a commit on the search server (like a read only mode) Things to watch out for, you will get stale NFS problem, I replaced lucene core that is shipped with solr to the latest one and it works. -----Original Message----- From: Jae Joo [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 13, 2007 9:06 AM To: solr-user Subject: two solr instances - index and commit Hi, I have two solr instance running under different tomcat environment. One solr instance is for indexing and would like to commit to the other solr instance. This is what I tried, but failed. using post.sh (without commit), the docs are indexed in solr-1 instance. After indexed, call commit command with the attribute of solr-2. Can any help me? Jae
