Sorry if this seems naïve (I am new to Lucene), but why not keep one copy of
the Lucene index on a NAS and have it shared by all servers?
-Original Message-
From: Biggy [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 27, 2006 7:57 AM
To: java-user@lucene.apache.org
Subject: Cluster
Well try having say 30 servers try to write in the index at the same time and
10 others
to read. You'll get enough locks to make a grown man cry. :)
Scott Sellman wrote:
>
> Sorry if this seems naïve (I am new to Lucene), but why not keep one copy
> of the Lucene index on a NAS and have it sha
I am new to this too. But my plan is to use sth like this:
I will use and online and offline index. Offline index will be presented
to search engine users and offline index will be updated continuously.
Time to time offline index will be written over online index. (When
update is considered to
Simply using NAS as just another file directory will cause these
locks. You need to use your own logic to control when to re-open the
index reader.
I think you can look into Nutch's distributed file system to see
whether that can help.
--
Chris Lu
-
Instant Full-Text Searc
Some quick questions/points:
What is the update rate?
The number of nodes you described is no problem, the query rate would be
no problem too (because they use read locks and act independently).
Do all nodes do updates or just 1? How often do these updates occur?
Probably best thing to do is g
Adam
> Date: Wed, 27 Dec 2006 10:46:47 -0800
> From: [EMAIL PROTECTED]
> To: java-user@lucene.apache.org
> Subject: Re: Clustering Lucene with 40 Servers
>
> Some quick questions/points:
>
> What is the update rate?
>
> The number of nod
On 12/28/06, Adam Fleming <[EMAIL PROTECTED]> wrote:
I saw that Doug Cutting had an interesting solution for his Technorati website:
http://www.mail-archive.com/lucene-user@jakarta.apache.org/msg12709.html
It sounds like it's a single-writer, many readers type of system, but quite
robust and ef
Not quite yet gone up to this scale but here are some points for
consideration based on a smaller scale system I have in production that
may be of interest:
By clustering I presume you are only talking about replication.
When we talk about scaling and using multiple machines we need to think
s? ...) before others can make useful
suggestions.
Otis
- Original Message
From: Adam Fleming <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Thursday, December 28, 2006 2:33:37 AM
Subject: RE: Clustering Lucene with 40 Servers
Hello,
I saw that Doug Cutting had an int
Hello,
Don't have any of the scalability requirements mentioned in this
thread but the problem is an interesting one.
Lucene needs a connection pool equivalent IMHO or a best practices
method for load balancing.
Opening, locking, reading and writing to remote indexes over RMI
seems good o
I don't know if terracotta is the right solution for you or not but...
--> Their examples talk of a 4 node cluster. This is way too small for my needs.
No 4 node limit. It was just a sample probably.
Cheers,
Steve
-Original Message-
From: Biggy [mailto:[EMAIL PROTECTED]
Sent: Wednesday
11 matches
Mail list logo
