Thanks for the response. My notes are below:
djlfldj
Hi Michael, in theory (I've never done it, either) what you're doing is correct
and exactly what I'd have done. I.e. use only one of the solr instances to
store data for both instances. When you get it working you can even manually
export the previous data from the orphan solr instance to the shared one.
You correctly allowed and tested access to server1 from server2.
On Jan 12, 2013 2:26 AM, "Michael Reynolds" <reyno...@uw.edu> wrote:
> But how to get dspace on server2 to send its solr client search statistics
> to server1? I tried setting the "server" property in
> modules/solr-statistics.cfg on server2 to
> "server=http://server1/solr/statistics";. That didn't work -- from
> "netstat -an" on server2 I could see connections from 127.0.0.1:<some port>
> to 127.0.0.1:8080 when I did searches, so clearly dspace on server2 was
> ignoring my "server" setting.
There must be some subtle problem in this part. It seems correct to me. I
assume you did restart Tomcat after changing configuration. And of course it
must be done in [dspace]/config, not [dspace-source]/dspace/config.
As you noted, the original setting (use solr on localhost) is still in effect.
Perhaps you accidentally have solr-statistics.server property set in
dspace.cfg?
> (And why not, since the ip address for
> server1 was not bound here!)
I didn't understand this part.
------------------------------------------------------------------------------
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
