-Re: Multiple Update servers
Otis Gospodnetic 2008-08-01, 16:29
SAN (or NAS if you can live with its performance) is one way. Oh course, the SAN would have to have redundant hw, too - no use in having multiple and redundant disks if you only have 1 controller, for example. Another options (that I have not tried) is DRBD. Whatever the case, you need to have only 1 active master. Have a look at one of the comments towards the end of SOLR-561 for a decent description of how this could be set up. ZooKeeper might help with active/standby coordination, too, I imagine.
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
----- Original Message ----
> From: Rakesh Godhani <[EMAIL PROTECTED]>
> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Sent: Monday, July 28, 2008 2:25:00 PM
> Subject: Multiple Update servers
> Hi, we are currently evaluating Solr and have been browsing the archives for
> one particular issue but can¹t seem to find the answer, so please forgive me
> if I¹m asking a repetitive question. We like the idea of having multiple
> slave servers serving up queries and a master performing updates. However
> the the issue for us there is no redundancy for the master. So a couple of
> 1. Can there be multiple masters (or update servers) sharing the same index
> files, performing updates at the same time (ie. Hosting the index on a SAN)?
> 2. Is there a recommended architecture utilizing a SAN. (For example 2
> slaves and 2 masters sharing a SAN). We current don¹t have that many
> records prob about a million and growing. We are mainly concerned about
> redundancy, then performance.