Yeah, it's another JEE deployment.
Looks like CF is running SOLR on a Jetty servlet engine. It may be a case of
going into /opt/webapps/ and making a copy of solr.war and call it something
new (say uat.war), and then restarting it.
You will have to look at having seperate solr.home's defined for
Barry, this is indeed interesting. I've read the other replies so far, and I
have some other thoughts.
I've not tried to install solr on a server where I installed CF in
multiserver mode, but looking at the install guide, it's a little unclear.
It says in the discussion of J2EE deployment (which
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
of those two routes. Sorry I couldn’t help more.
/charlie
*From:* cfaussie@googlegroups.com [mailto:cfaussie@googlegroups.com] *On
Behalf Of *Barry Chesterman
*Sent:* Tuesday, April 05, 2011 5:15 PM
*To:* cfaussie@googlegroups.com
*Subject:* Re: [cfaussie] using Solr in a multi instance
I had a look the other day, and it looks like cf's solr configuration is
multi core, so you can set up more than one index on there. You don't need a
whole other solr instance running.
I'm doing a lot of solr work at the moment, and found it much easier to
simply setup an instance of the latest
Yes, we have several indexes in Solr e.g.
majors
papers
The only problem is, our second instance needs to use the same collection
names which means we can't just point the second instance to the same place.
On Tue, Apr 5, 2011 at 9:42 AM, Mark Mandel mark.man...@gmail.com wrote:
I had a look
Oh, I think I see the issue.
You want to deploy a second instance of solr, but are not sure how to tell
each instance to have different solr homes. Is that correct?
Mark
Sent from my mobile device.
On 05/04/2011 8:07 AM, Barry Chesterman barrychester...@gmail.com wrote:
--
You received this
Deploying a second instance of solr was my idea also, but I wasn't sure if
this was the right way to go about it or not (I'm also not exactly sure how
you go about deploying a second instance of Solr either) - is it a copy
directory and modify some files type exercise, or is it a run the solr