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, Cr
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
FYI, CDCR support, as it exists in Solr today, has been deprecated in 8.6.
It suffers from serious design flaws and it allows such things to happen
that you observe. While there may be workarounds, it is advisable to not
rely on CDCR in production.
Thanks,
Ishan
On Thu, 2 Jul, 2020, 1:12 am Oakle
For the record, it is not just Solr7.4 which has the problem. When I start
afresh with Solr8.5.2, both symptoms persist.
With Solr8.5.2, tlogs accumulate endlessly at the non-Leader nodes of the
Source SolrCloud and are never released regardless of maxNumLogsToKeep setting
And with Solr8.5.2, i
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