Thanks, Tom. Is that correct that i have to execute this for each shard?
On Thu, Apr 26, 2018 at 10:19 AM, Tom Peters <tpet...@synacor.com> wrote:
> I'm not sure under what conditions it will be automatically triggered, but
> if you manually wanted to trigger a CDCR Bootstrap you n
I'm not sure under what conditions it will be automatically triggered, but if
you manually wanted to trigger a CDCR Bootstrap you need to issue the following
query to the leader in your target data center.
/solr//cdcr?action=BOOTSTRAP=
The masterUrl will look something like (change
Anybody has idea how to trigger Solr CDCR BOOTSTRAP or under what condition
it gets triggered ?
Thanks,
Susheel
On Tue, Apr 24, 2018 at 12:34 PM, Susheel Kumar <susheel2...@gmail.com>
wrote:
> Hello,
>
> I am wondering under what different conditions does that CDCR bootstrap
Hello,
I am wondering under what different conditions does that CDCR bootstrap
process gets triggered. I did notice it getting triggered after I stopped
CDCR and then started again later and now I am trying to reproduce the same
behavior.
In case target cluster is left behind and buffer
269
> > www.lucidworks.com
> > Twitter http://twitter.com/lucidworks
> > LinkedIn: https://www.linkedin.com/in/sarkaramrit2
> > Medium: https://medium.com/@sarkaramrit2
> >
> > On Mon, Apr 16, 2018 at 11:35 PM, Susheel Kumar <susheel2...@gmail.com>
> > wrote:
>
/medium.com/@sarkaramrit2
>
> On Mon, Apr 16, 2018 at 11:35 PM, Susheel Kumar <susheel2...@gmail.com>
> wrote:
>
>> Does anybody know about known issue where CDCR bootstrap sync leaves the
>> replica's on target cluster non touched/out of sync.
>>
>> A
/@sarkaramrit2
On Mon, Apr 16, 2018 at 11:35 PM, Susheel Kumar <susheel2...@gmail.com>
wrote:
> Does anybody know about known issue where CDCR bootstrap sync leaves the
> replica's on target cluster non touched/out of sync.
>
> After I stopped and restart CDCR, it builds my ta
Does anybody know about known issue where CDCR bootstrap sync leaves the
replica's on target cluster non touched/out of sync.
After I stopped and restart CDCR, it builds my target leaders index but
replica's on target cluster still showing old index / not modified.
Thnx
on:
> KeeperErrorCode = Session expired for /collections/sial-catalog-
> product/state.json
>
> So is Zookeeper hosed? How do I tell?
>
> On Tue, Jul 4, 2017 at 3:27 PM, Webster Homer <webster.ho...@sial.com>
> wrote:
>
>> We've been using cdcr for a while now. It
this:
> 2017-07-04 14:41:27.015 ERROR (cdcr-bootstrap-status-51-
> thread-1-processing-n:dfw-pauth-msc02:8983_solr) [ ]
> o.a.s.h.CdcrReplicatorManager Exception during bootstrap status request
>
> In this case we have one server throwing the above errors a lot!
>
> The error i
We've been using cdcr for a while now. It seems to be pretty fragile.
Currently we're seeing tons of errors like this:
2017-07-04 14:41:27.015 ERROR
(cdcr-bootstrap-status-51-thread-1-processing-n:dfw-pauth-msc02:8983_solr)
[ ] o.a.s.h.CdcrReplicatorManager Exception during bootstrap status
11 matches
Mail list logo