In our environment, we use a mirrored pair of dspace tomcat servers behind
an ipvs cluster server for redundancy and throughput. The two servers share
the same general settings, assetstores, and postgres database. All works
well, except that of course the user search statistics are gathered
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
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
(realize I never did summarize my setup, so here it is...)
***Our environment ***
* Dspace version 1.8.2
* Tomcat 5.5
* Redhat release 5.8
* Two separate linux hosts running dspace, both behind a
director/ipvs/heartbeat/load-balancing bastion host. all queries
load-balanced between the two
Thank you both for your helpful replies! So, to summarize:
* Running separate generic apache solr server is doable
* Although ideal approach would be to use solr server 4.0 to take
advantage of the cloud capability, there are compatibility problems
with the index structure of dspace 3.0 that
5 matches
Mail list logo
