We are getting ready to start a project using Solr as our backend search engine and I am trying to devise a deployment architecture that works for us. We definitely need a master/slave replication strategy, that's for sure, but my concern is the master becomes a single point of failure.
Fortunately, real-time search is not a requirement for us. If search results are a few minutes out of sync with our database, it's not a big deal. So what I would like to do is have a set of query servers (slaves) that are only used for querying, no indexing and have them use Solr's HTTP replication mechanism on a 2 or 3 minute interval. To get HA indexing, I'd like to have 2 masters: a primary and a standby. All indexing requests go to the primary unless it's taken out of service. To keep the standby ready to takeover if it needs to, it needs to be more up to date than the slaves. I'd like to have it replicate every 30 seconds or so. The reason I'm asking about it on this list is that I haven't seen any Solr documentation or even anything that talks about this. I can't be the only one concerned about having a single point of failure, so I'm reaching out to see what others have done in this case before I go with my own solution. Brandon Ramirez | Office: 585.214.5413 | Fax: 585.295.4848 Software Engineer II | Element K | www.elementk.com<http://www.elementk.com/>
