Comments on: Making acts_as_solr Act As Deployable http://jasonrudolph.com/blog/2007/11/26/making-acts_as_solr-act-as-deployable/ puts Blog.new("nonsense") Thu, 04 Dec 2008 18:21:24 +0000 http://wordpress.org/?v=2.6.3 By: Jason Rudolph http://jasonrudolph.com/blog/2007/11/26/making-acts_as_solr-act-as-deployable/#comment-12542 Jason Rudolph Tue, 27 Nov 2007 11:34:55 +0000 http://jasonrudolph.com/blog/2007/11/26/making-acts_as_solr-act-as-deployable/#comment-12542 <p>Thanks, Hoss.<br /> <br /> My apologies. I should have been more clear in my original statement. I wanted to make sure that people didn't make the same mistake I made at first: attempting to allow multiple Solr instances to <em>write</em> to a single set of indexes. Ouch! (Many thanks to Erik Hatcher for quickly showing me the error of my ways with regards to that admittedly naive setup.) I've updated the post to warn against this potential mistake while still informing people about the availability of a proper distributed setup, in case they should have a need for running multiple Solr instances.<br /> <br /> Thanks again,<br /> Jason</p> Thanks, Hoss.

My apologies. I should have been more clear in my original statement. I wanted to make sure that people didn't make the same mistake I made at first: attempting to allow multiple Solr instances to write to a single set of indexes. Ouch! (Many thanks to Erik Hatcher for quickly showing me the error of my ways with regards to that admittedly naive setup.) I've updated the post to warn against this potential mistake while still informing people about the availability of a proper distributed setup, in case they should have a need for running multiple Solr instances.

Thanks again,
Jason

]]> By: Hoss http://jasonrudolph.com/blog/2007/11/26/making-acts_as_solr-act-as-deployable/#comment-12518 Hoss Tue, 27 Nov 2007 05:54:36 +0000 http://jasonrudolph.com/blog/2007/11/26/making-acts_as_solr-act-as-deployable/#comment-12518 <p>I know very little about ruby, and less about rails -- but most of the advice here about not running Solr on multiple machines is very misleading.</p> <p>It is very feasible to run multiple Solr instances that you query against and have them all "slave" off of a single Solr "master" (just as you might set up Database replication with MySql etc...)</p> <p>The user doesn't have to "manage multiple sets of Solr indexes and try to make sure they all have the same data" -- Solr (and a few simple crontab entries) can/will take care of all of that if you want it to...</p> <p>http://wiki.apache.org/solr/CollectionDistribution</p> <p>(BTW, on an unrelated note: the dataDir option in the solrconfig.xml file allows you to pick any arbitrary path for storing the index)</p> I know very little about ruby, and less about rails — but most of the advice here about not running Solr on multiple machines is very misleading.

It is very feasible to run multiple Solr instances that you query against and have them all “slave” off of a single Solr “master” (just as you might set up Database replication with MySql etc…)

The user doesn’t have to “manage multiple sets of Solr indexes and try to make sure they all have the same data” — Solr (and a few simple crontab entries) can/will take care of all of that if you want it to…

http://wiki.apache.org/solr/CollectionDistribution

(BTW, on an unrelated note: the dataDir option in the solrconfig.xml file allows you to pick any arbitrary path for storing the index)

]]>