Instead of CDCR you may simply duplicate the pipeline across both data centers.
Then there is no need at each step of the pipeline to replicate (storage to
storage, index to index etc.).
Instead both pipelines run in different data centers in parallel.
> Am 24.06.2020 um 15:46 schrieb Oakley,
Yes, I saw that yesterday.
I guess that I was not the only one who noticed the unreliability after all.
-Original Message-
From: Ishan Chattopadhyaya
Sent: Friday, July 17, 2020 1:17 AM
To: solr-user
Subject: Re: CDCR stress-test issues
FYI, CDCR support, as it exists in Solr today
t; Sent: Wednesday, June 24, 2020 9:46 AM
> To: solr-user@lucene.apache.org
> Subject: CDCR stress-test issues
>
> In attempting to stress-test CDCR (running Solr 7.4), I am running into a
> couple of issues.
>
> One is that the tlog files keep accumulating for some nodes in th
added after the missing records).
Does anyone yet have any suggestion how to get CDCR to work properly?
-Original Message-
From: Oakley, Craig (NIH/NLM/NCBI) [C]
Sent: Wednesday, June 24, 2020 9:46 AM
To: solr-user@lucene.apache.org
Subject: CDCR stress-test issues
In attempting
On Wed, Jun 24, 2020 at 9:46 AM Oakley, Craig (NIH/NLM/NCBI) [C]
wrote:
>
> In attempting to stress-test CDCR (running Solr 7.4), I am running into a
> couple of issues.
>
> One is that the tlog files keep accumulating for some nodes in the CDCR
> system, particularly for the non-Leader nodes
In attempting to stress-test CDCR (running Solr 7.4), I am running into a
couple of issues.
One is that the tlog files keep accumulating for some nodes in the CDCR system,
particularly for the non-Leader nodes in the Source SolrCloud. No quantity of
hard commits seem to cause any of these tlog
