AS 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: Clustering Lucene with 40 Servers
>
>
> I'm currently investigat
I'm currently investigating the best ways of clustering Lucene.
I've heard of both Solr, Terracotta but do not know how well they scale.
Their examples talk of a 4 node cluster. This is way too small for my needs.
I have 30x JVMs each handling 3 requests/sec and each having their own
Lucene index
know the
> internals of Lucene well enough to predict. Neither do I BTW...) you're
> creating complexity which you don't know is necessary. I'd only go there
> if
> doing it the straight-forward way shows performance issues. I'd also bet
> that any performance i
OK here what i've come up with - After reading your suggestions
- bit set from DB stays untouched
- only one field shall be used to store interest field bits in the document:
"interest". Saves disk space.
- The bits shall be not be converted to readable string but added as values
separated by spa
i have the same problem here. I have an interest bit field, which i
receive from the applciation backend. I have control over how the docuemtns
are built.
To be specific, the field looks like this:
ID: interest
1 : sport
2 : music
4 : film
8 : clubs
So someone interested in sports and music ca
