Hi Yury,
How do you manage to start the instances without any issues? The way I see
it, no matter which instance is started first, the slave will complain about
not being to find its respective master because that instance hasn't been
started yet ... no?
Thanks,
- Pulkit
2011/5/17 Yury Kats
Sorry, stupid question, now I see that the core still starts and the polling
process simply logs an error:
SEVERE: Master at: http://localhost:7574/solr/master2/replication is not
available.
Index fetch failed. Exception: Connection refused
I was able to setup the instructions in-detail with
On 9/10/2011 3:54 PM, Pulkit Singhal wrote:
Hi Yury,
How do you manage to start the instances without any issues? The way I see
it, no matter which instance is started first, the slave will complain about
not being to find its respective master because that instance hasn't been
started yet
Hi,
I have two Solr nodes, each managing two cores -- a master core and a slave
core.
The slaves are setup to replicate from the other node's masters
That is, node1.master - node2.slave, node2.master - node1.slave.
The replication is configured in each core's solrconfig.xml, eg
Master's
Yury,
perhaps Java-Pararms (like used for this sample:
http://wiki.apache.org/solr/SolrReplication#enable.2BAC8-disable_master.2BAC8-slave_in_a_node)
can help you?
Regards
Stefan
2011/5/17 Yury Kats yuryk...@yahoo.com:
Hi,
I have two Solr nodes, each managing two cores -- a master core and a
On 5/17/2011 10:17 AM, Stefan Matheis wrote:
Yury,
perhaps Java-Pararms (like used for this sample:
http://wiki.apache.org/solr/SolrReplication#enable.2BAC8-disable_master.2BAC8-slave_in_a_node)
can help you?
Ah, thanks! It does seem to work!
Cluster's solrconfig.xml (shared between all
