Hi,
Were running a cloud based cluster of servers and its not that easy to
get a list of the current slaves. Since my problem is only around the
restart/redeployment of the master it seems an unnecessary
complication to have to start interacting with slaves as part of the
scripts that do this.
Having played with it, I can see that it would be extremely useful to be
able to disable replication in the solrconfig.xml, and then enable it
with a URL.
So, as to your patch, I'd say yes, submit it. But do try to make it
backwards compatible. It'll make it much more likely to get accepted.
Hi,
I am looking into using a multi core configuration to allow us to
fully rebuild our index while still applying updates.
I have two cores main-core and rebuild-core. I push the whole dataset
into the rebuild core, during which time I can happily keep pushing
updates into the main-core. Once
I've just done a bit of playing here, because I've spent a lot of time
reading the SolrReplication wiki page[1], and have often wondered how
some features interact.
Unfortunately, if you specify str name=enablefalse/str in your
replication request handler for your master, you cannot re-enable it
