Hi Shalin,
I did try to do that but it hadn't made any difference, the remote clusters did
not update. Autocommit is already set on the remote clusters as follows:
<autoCommit>
<maxTime>${solr.autoCommit.maxTime:150000}</maxTime>
<maxDocs>10000</maxDocs>
<openSearcher>true</openSearcher>
</autoCommit>
I can also see in the Solr admin pages, there is a warn message with
CdcrUpdateLogSynchronizer - Caught unexpected exception. That's all I can see
at the moment. No errors apart from that.
Thanks,
Daniel
-----Original Message-----
From: Shalin Shekhar Mangar <shalinman...@gmail.com>
Sent: 29 November 2020 05:19
To: solr-user@lucene.apache.org
Subject: Re: CDCR
EXTERNAL EMAIL - Be cautious of all links and attachments.
If you manually issue a commit operation on the remote clusters, do you see any
updates? If yes, then you should set autoCommit on the remote clusters.
If no, then check the logs on the cluster which is receiving the indexing
operations and see if there are any errors.
On Wed, Nov 25, 2020 at 6:11 PM Gell-Holleron, Daniel <
daniel.gell-holle...@gb.unisys.com> wrote:
> Hello,
>
> Does anybody have advice on why CDCR would say its Forwarding updates
> (with no errors) even though the solr servers its replicating to
> aren't updating?
>
> We have just under 50 million documents, that are spread across 4 servers.
> Each server has a node each.
>
> One side is updating happily so would think that sharding wouldn't be
> needed at this point?
>
> We are using Solr version 7.7.1.
>
> Thanks,
>
> Daniel
>
>
--
Regards,
Shalin Shekhar Mangar.
