We run multiple, identical, independent copies. No master/slave dependencies. Yes, we run indexing N times for N servers, but that's what CPU is for and I sleep better at night. It makes testing and deployment trivial, too.
wunder == Walter Underwood Search Guy, Netflix On 10/8/07 4:05 AM, "Daniel Alheiros" <[EMAIL PROTECTED]> wrote: > Hi > > I'm about to deploy SOLR in a production environment and so far I'm a bit > concerned about availability. > > I have a system that is responsible for fetching data from a database and > then pushing it to SOLR using its XML/HTTP interface. > > So I'm going to deploy N instances of my application so it's going to be > redundant enough. > > And I'm deploying SOLR in a Master / Slaves structure, so I'm using the > slaves nodes as a way to keep my index replicated and to be able to use them > to serve my queries. But my problem lies on the indexing side of things. Is > there a good alternative like a Master/Master structure that I could use so > if my current master dies I can automatically switch to my secondary master > keeping my index integrity? Or it would be needed a manual index merge after > this switch over so I can redefine my primary master server? > > Thanks, > Daniel > > > http://www.bbc.co.uk/ > This e-mail (and any attachments) is confidential and may contain personal > views which are not the views of the BBC unless specifically stated. > If you have received it in error, please delete it from your system. > Do not use, copy or disclose the information in any way nor act in reliance on > it and notify the sender immediately. > Please note that the BBC monitors e-mails sent or received. > Further communication will signify your consent to this. >
