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 solr on jetty, and talk to it via solrj loaded in JavaLoader, than screw around with cf's version.
Mark
Sent from my mobile device.
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.
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 is different from
multiserver) that "there can be only one solr instance per server". It
doesn't really seem to speak to multiserver deployment.
But it does say (as Mark did) that at least in that J2EE setup, the solution
is for it to be in one place and for the solr home in each CF admin to be
configured to point to that place.
I'm curious: do I assume you did tell it to install Solr during the CF 9
Multiserver installation, right? I'm curious: where did the solr files end
up? In a Standard/Server deployment, they are in a [cf]\solr directory. In a
multiserver deployment, was this created within the cfusion instance (such
as a C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\cfusion\solr
directory), or perhaps even also in each new isntance (such as in
C:\JRun4\servers\instance2\cfusion.ear\cfusion.war\WEB-INF\cfusion\solr)? Or
is it put in some directory outside of jrun entirely?
If it was created each instance, then I wonder if it may be possible for you
to manually manipulate the solr/jetty config files to simply specify
different ports so that they can run on their own. It seems reasonable. But
I wouldn't be surprised if the CF team opted to make the default behavior be
simplest: a single deployment.
Hope that helps. Let us know what you find.
/charlie
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
--
You received this message because you are subscribed to the Google Groups "cfaussie" group.
To post to this group, send email to cfau...@googlegroups.com.
To unsubscribe from this group, send email to cfaussie+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
Just today a client asked me for a searchable document repository.
Great timing.
Rawdy
On Wednesday, April 6, 2011, Mark Mandel <mark....@gmail.com> wrote:
> Just as an aside - if anyone is looking to seriously get into Solr, I cannot recommend this book enough:
> http://www.packtpub.com/solr-1-4-enterprise-search-server/book
>
> Solr is an amazing product, but its online documentation can be lacking. The above book really takes you end to end with Solr, and shows you pretty much everything that can be done with it, from features, through to deployment.
>
> Mark
>
--
*Rawdyn Nutting*
Chief Technology Officer
*CODEBASE Pty Ltd*
codebase.com.au
1300 596 400