: distributed architecture
Date: Wed, 1 Dec 2010 00:39:40 +
I cannot say how mature the code for B) is, but it is not yet included
in a release.
If you want the ability to distribute content across multiple nodes (due
to volume) and want resilience, then use both.
I've had one setup
On Tue, 30 Nov 2010 23:11 -0800, Dennis Gearon gear...@sbcglobal.net
wrote:
Wow, would you put a diagram somewhere up on the Solr site?
Or, here, and I will put it somewhere there.
I'll see what I can do to make a diagram.
And, what is a VIP?
Virtual IP. It is what a load balancer uses. You
Hi,
also take a look at solandra:
https://github.com/tjake/Lucandra/tree/solandra
I don't have it in prod yet but regarding administration overhead it
looks very promising.
And you'll get some other neat features like (soft) real time, for free.
So its same like A) + C) + X) - Y) ;-)
Hi,
thanks all, this has been very instructive. It looks like in the short
term using a combination of replication and sharding, based on Upayavira's
setup, might be the safest thing to do, while in the longer term following the
zookeeper integration and solandra development might
I cannot say how mature the code for B) is, but it is not yet included
in a release.
If you want the ability to distribute content across multiple nodes (due
to volume) and want resilience, then use both.
I've had one setup where we have two master servers, each with four
cores. Then we have two
On 11/30/2010 2:27 PM, Cinquini, Luca (3880) wrote:
Hi,
I'd like to know if anybody has suggestions/opinions on what is
currently the best architecture for a distributed search system using Solr. The
use case is that of a system composed
of N indexes, each hosted on a separate machine,
Hi, A diagram will be very much appreciated.
Thanks,
Jayant
From: u...@odoko.co.uk
To: solr-user@lucene.apache.org
Subject: Re: distributed architecture
Date: Wed, 1 Dec 2010 00:39:40 +
I cannot say how mature the code for B) is, but it is not yet included
in a release.
If you
, November 30, 2010 4:39:40 PM
Subject: Re: distributed architecture
I cannot say how mature the code for B) is, but it is not yet included
in a release.
If you want the ability to distribute content across multiple nodes (due
to volume) and want resilience, then use both.
I've had one setup where
4 big indices if those servers can handle them.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Woytowitz, Matthew matthew.woytow...@mantech.com
To: solr-user@lucene.apache.org
Sent: Tuesday, May 26, 2009 1:01:48 PM
Subject: Distributed
