is used as a fall-back when
>> a replica syncs, but there'll be some bits like this hanging around I'd
>> guess.
>>
>> Best,
>> Erick
>>
>> On Thu, Oct 19, 2017 at 11:55 PM, Hendrik Haddorp
>> wrote:
>>>
>>> Hi Erick,
>>
here'll be some bits like this hanging around I'd guess.
Best,
Erick
On Thu, Oct 19, 2017 at 11:55 PM, Hendrik Haddorp
wrote:
Hi Erick,
that is actually the call I'm using :-)
If you invoke
http://solr_target_machine:port/solr/core/replication?command=details after
that you can see
ct 19, 2017 at 11:55 PM, Hendrik Haddorp
wrote:
> Hi Erick,
>
> that is actually the call I'm using :-)
> If you invoke
> http://solr_target_machine:port/solr/core/replication?command=details after
> that you can see the replication status. But even after a Solr restart the
Hi Erick,
that is actually the call I'm using :-)
If you invoke
http://solr_target_machine:port/solr/core/replication?command=details
after that you can see the replication status. But even after a Solr
restart the call still shows the replication relation and I would like
to remove th
Little known trick:
The fetchIndex replication API call can take any parameter you specify
in your config. So you don't have to configure replication at all on
your target collection, just issue the replication API command with
masterUrl, something like:
http://solr_target_machine:port/solr
Hi,
I want to transfer a Solr collection from one SolrCloud to another one.
For that I create a collection in the target cloud using the same config
set as on the source cloud but with a replication factor of one. After
that I'm using the Solr core API with a "replication?command=fetchindex"