Hi Mark, Would it work to pus something like Apache (or any LB or any other simpler tool) in front of your cluster and configure it to use mod_proxy or mod_rewrite to pass requests to appropriate backend Tomcat instance depending on the original URL?
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Mark A. Matienzo <mark.matie...@gmail.com> > To: solr-user@lucene.apache.org > Sent: Friday, June 19, 2009 11:42:41 AM > Subject: Replication in Solr 1.4 - redirecting update handlers? > > I'm trying to figure out the best solution to the following issue. > We've got three boxes in our replication set up - one master and two > load balanced slaves, all of which serve Solr using Tomcat. Given > this setup, we're also using the Drupal apachesolr module, which > currently supports only one "Solr host" in its configuration. What is > the best way to make this transparent to the Drupal module? Is it > possible to have some sort of phony update handler to redirect the > update requests to the master box from within Solr, or is this > something that would be more properly implemented in the Tomcat > configuration? > > Mark A. Matienzo > Applications Developer, Digital Experience Group > The New York Public Library
