Thanks for the clarifications/confirmations/observations. Sounds like you will indeed need to go one of those two routes. Sorry I couldn't help more.
/charlie From: [email protected] [mailto:[email protected]] On Behalf Of Barry Chesterman Sent: Tuesday, April 05, 2011 5:15 PM To: [email protected] Subject: Re: [cfaussie] using Solr in a multi instance configuration Thanks for the info Mark, and yes you can point coldfusion to a seperate solr instance. Charlie, when the initial install was done, it was a multiserver deployment. Yes it goes in the directory you mention below, in the default cfusion instance in: /opt/jrun4/servers/cfusion/.. The Solr part is installed at: /opt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/WEB-INF/cfusion/solr/ and there is a start script that gets put in init.d/ to start / stop / restart solr. Yes solr was installed in the initial deployment and we have been using it without a problem in that instance. When the second instance creation was done, we just ran the create new instance from the CFIDE administrator, and then did the custom apache config edits as listed in the cf9 documentation. It creates the second instance here: /opt/jrun4/servers/uat/ I looked in the corresponding folder as the default install, and there is no solr/ folder in /opt/jrun4/servers/uat/cfusion.ear/cfusion.war/WEB-INF/cfusion/ We are not sure what one is 'supposed' to do here, normally I guess you would have your second instance just point to the solr server running from the default install instance, but in our case this is no good because we need to use the same collection names for the second instance. I had a go at running multiple webapps with Jetty (what Solr in cf runs on) - where you edit the [CF]/solr/etc/jetty.xml config file as shown here: http://wiki.apache.org/solr/SolrJetty but none of that worked, Solr would always fail to start with errors, normally about how it couldn't find the methods or classes specified. Solr under coldfusion runs the collections out of a [CF]/solr/multicore The only options I've come up with are; 1. copy the solr folder from the cfusion instance, to our uat instance, and update the jetty config accordingly, add a new solr start file in init.d and update the new coldfusion instance to point to that solr server. 2. run the installer for the standalone solr server (which adobe provide mainly for running solr on a different server), then point the new coldfusion instance to that - essentially what Mark pointed out in his post. Barry -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
