On Feb 25, 2010, at 12:54 AM, Andrew Bruno wrote:
> Since the disk IO on the server is high, our datacenter engineers suggested
> we look at NAS or SAN, for performance gain, and for future growth.
Alternatively, get a stack of RamSan and call it a day:
http://www.ramsan.com/products/products.h
NFS. It works fine for simple essentially static lucene indexes and
we still use it for that, but things tended to fall apart with dynamic
indexes.
--
Ian.
On Fri, Feb 26, 2010 at 11:06 AM, Marcelo Ochoa wrote:
> Hi Ian:
> Only as curiosity ;)
> Which distributed file system are you using o
Hi Ian:
Only as curiosity ;)
Which distributed file system are you using on top of your NAS storage?
Best regards, Marcelo.
On Thu, Feb 25, 2010 at 6:54 AM, Ian Lea wrote:
> We've run lucene on NAS, although not with indexes anything like as
> large as 1Tb, and gave up because NFS and lucen
To my experience, some customers used SAN to store the index. It's
pretty good and fast. This may be a good choice for you, but it's costly.
--
--
Chris Lu
-
Instant Scalable Full-Text Search On Any Database/Application
site: http://www.dbsight.net
demo: http://search.db
Katta looks interesting. I have also been looking at SOLR, but both of
these require reworking the application, and possibly re-indexing the world
again.
Do you know if Katta supports Compass/Lucene v2.0 migration?
Also, when I say 1T, what I really mean is that we have about 1200 different
inde
We've run lucene on NAS, although not with indexes anything like as
large as 1Tb, and gave up because NFS and lucene don't really work
very well together. Google for "lucene nfs" for some details, and some
workarounds.
I'd second Kay Kay's suggestion to look at a distributed solution such as Katta
It might be useful to check out katta , from an infrastructure perspective.
On 2/24/10 3:54 PM, Andrew Bruno wrote:
Hello,
I am working with an application that offers its customers their own index,
primary two indexes for different needs per customer.
As our business is growing and growing,
Hello,
I am working with an application that offers its customers their own index,
primary two indexes for different needs per customer.
As our business is growing and growing, I now have a situation where the web
application has its customer's index on one volume, and its getting close to
1Tbyte
