We had a similar issue using acts_as_solr. We already had lighttpd
running on some servers so we just proxied all requests for /solr/CORE/
update to the master and /solr/CORE/select to a load balanced IP for
our slaves.
Doug
On Jun 19, 2009, at 11:42 AM, Mark A. Matienzo wrote:
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
