Correct, but if you are using a distributing index, you should make
copies of it, not access the same index (on one machine) from
multiple machines. If doing this, you would still need some sort of
server process on the master, and if that is available, it can
control the distribution of the index - so once again, no problem
with NFS do to renames, etc.
I guess I just don't see how any NFS issues should matter in a
properly deployed Lucene - even multiserver - environment.
It is similar to the class reason why unix databases never used/
needed file locks - the server process managed the locks internally -
which is far more efficient.
On Sep 15, 2006, at 9:49 AM, Yonik Seeley wrote:
On 9/15/06, robert engels <[EMAIL PROTECTED]> wrote:
Why not just use a dedicated server with an HTTP/TCP listener and let
it respond to Lucene queries.
If you have more than one server to handle the load, you need to
distribute the index to all the search boxes. NFS is an easy way, but
I imagine performance would suffer.
Solr can use rsync to update each server with the segment changes, but
other methods like letting NFS handle it are possible.
-Yonik
http://incubator.apache.org/solr Solr, the open-source Lucene
search server
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
