Sorry for my previous abortive reply! Grrr, trying to figure out Windows
Live Mail formatting -- never mind, using gmail instead...
Thanks, helix84, for your reply. My comments are below...
On Sat, Jan 12, 2013 at 2:34 AM, helix84 <heli...@centrum.sk> wrote:
> 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.
>
> Yup, changed in the production dspace directory and restarted tomcat. I'm
puzzled a bit, though, as to why you're puzzled it didn't work. The docs
(rather ambiguously) say that the "server" property defines both where the
solr client sends statistics as well as where the solr server listens for
data. Since server2 does not own the server1 ip address, of course the
server2 solr server won't be able to listen at server1:8080. So I'd
figured the design of dspace simply wasn't set up for this; I just tried it
as a long shot. So you think it might actually work to specify another
server's ip address here? That would be great if I can get it to work.
> 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?
>
> Alas, no, it is set in modules/solr-statistics.cfg. However, your
comment prompted another thought: what about the modules/discovery.cfg?
There's the search.server setting there. Again, tho, the documentation
makes no mention of how to set this up for the server running on another
host. I had not tried setting that also to point to server1:8080. Worth a
try?
> > (And why not, since the ip address for
> > server1 was not bound here!)
>
> I didn't understand this part.
>
As mentioned above, I really didn't expect this to work, since the ip
address for server1 is not available on server2, so I didn't really expect
any of this to work on server2. Since the dspace docs are written in such
a way that they assume you are using a local ip address for this setting, I
had assumed that the design of dspace did not allow for this setting to
refer to a remote server. Do you have knowledge of the design of dspace
beyond the docs? I haven't had a chance to look through the dspace solr
java code myself.
Thanks again for your reply and for any advice! --Mike
------------------------------------------------------------------------------
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
