lucene-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Cutting <>
Subject Re: Infrastructure for large Lucene index
Date Tue, 10 Oct 2006 20:14:13 GMT
Chris Hostetter wrote:
> : 3. If you're worried about high availability, then one fairly simple
> : approach is to have two parallel set of search clusters, with a load
> : balancer in front. For each cluster, monitor both the front-end
> : server (where the results get combined) and each of the back-end
> : search servers - for example, something like Big Brother or Ganglia.
> : Then if one of the search servers (or, god forbid, the front end
> : server) goes down, you can automatically remove that cluster from the
> : load balancer's active set.
> the availability of this approach doesn't scale very cleanly though ... if
> any one box in either cluster goes down, the entire cluster becomes
> unusable.

A cost-effective variation works as follows: if you have 10 indexes and 
11 nodes, then you keep one node as a spare.  When any of the 10 active 
nodes fail, the 11th resumes its duties.  While the 11th node is 
launching you search only 9 out of the 10 indexes, so failover is not 
entirely seamless, but it's a lot cheaper than mirroring all nodes.


View raw message