Susheel, At the time of core reload, logs must be complaining or atleast pointing to some direction. Each leader of shard is responsible to spawn a threadpool for cdcr replicator to get the data over.
Amrit Sarkar Search Engineer Lucidworks, Inc. 415-589-9269 www.lucidworks.com Twitter http://twitter.com/lucidworks LinkedIn: https://www.linkedin.com/in/sarkaramrit2 Medium: https://medium.com/@sarkaramrit2 On Tue, Apr 17, 2018 at 9:04 PM, Susheel Kumar <susheel2...@gmail.com> wrote: > Hi, > > Has anyone gone thru this issue where few shard leaders are forwarding > updates to their counterpart leaders in target cluster while some of the > shards leaders are not forwarding the updates. > > on Solr 6.6, 4 of the shards logs I see below entries and their > counterpart in target are getting updated but for other 4 shards I don't > below entries and neither being replicated to target. > > Any suggestion on how / what can be done to start cdcr-replicator threads > on other shards? > > 2018-04-17 15:26:38.394 INFO > (cdcr-replicator-24-thread-6-processing-n:dc2prsrcvap0049. > whc.dc02.us.adp:8080_solr) > [ ] o.a.s.h.CdcrReplicator Forwarded 0 updates to target COLL > 2018-04-17 15:26:39.394 INFO > (cdcr-replicator-24-thread-7-processing-n:dc2prsrcvap0049. > whc.dc02.us.adp:8080_solr) > [ ] o.a.s.h.CdcrReplicator Forwarded 0 updates to target COLL > > Thanks > Susheel >
