Anson,
One way of doing it is having subsets of your indexes / data on
different machines. Each machine indexes its own data. You implement a
system that distributes queries to the various machines and merges the
results back.
The working well completely depends on your implementation of the
distributed search.
I believe there was a discussion about implementing this using a
MultiSearcher somewhere as well.
Cheers!
Jochen
-----Original Message-----
From: Anson Lau [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 22, 2004 2:17 PM
To: 'Lucene Users List'
Subject: RE: Lucene scalability/clustering
Further on this topic - has anyone tried implementing a distributed
search with Lucene? How does it work and does it work well?
Anson
-----Original Message-----
From: Hamish Carpenter [mailto:[EMAIL PROTECTED]
Sent: Monday, February 23, 2004 5:24 AM
To: Lucene Users List
Subject: Re: Lucene scalability/clustering
Hi All,
I'm Hamish Carpenter who contributed the benchmarks with the comment
about the IndexSearcherCache. Using this solved our issues with too
many files open under linux.
The original IndexSearcherCache email is here:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01967.html
See here for a copy of the above message and a download link:
http://www.geocities.com/haytona/lucene/
The mailing list doesn't like attachments. The source is 10K in size.
HTH
Hamish Carpenter.
[EMAIL PROTECTED] wrote:
> BTW, where can I get Peter Halacsy's IndexSearcherCache?
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
