Hi,
Running Solr 7.7.2, cluster with 3 replicas
When CDCR is enabled, one of the target nodes gets an incorrect recovery
request.
Below is the content of the state.json file from the zookeeper.
"shards":{"shard1":{
"range":"8000-7fff",
"state":"active",
Whenever I create a new collection on solr 7.7.2 cluster CDCR(uni
directional),
and once I disable buffer on both source and target nodes and start CDCR
process on the source node, then I encounter the error message "solr unable
to locate core..." on one of target node.
On source node, CDCR
Using solr 7.7.2.
Our CDCR is broken for some reason as I posted the other
question(https://lucene.472066.n3.nabble.com/Three-questions-about-huge-tlog-problem-and-CDCR-td4453788.html).
So the size of tlog is huge now... I don't care CDCR for now, and just want
to clean all these tlog first.
sure.
I disabled buffer and started cdcr by calling api on both side.
And when I do indexing, I see the size of tlog folder stays within 1MB while
the size of index folder is increasing.
So I imagined that tlog would be consumed by target node and cleared, and
data is being forwarded to target
Thank you for the advice.
By the way, when I upload a new collectin configuration to zookeepr and
enable bidirectional CDCR for the collections on both prod and dr
side(/cdcr?action=START), and reload the collections, CDCR
usually didn't work. So if I restarted entire nodes in the cluster on both
found a typo. correcting "updateLogSynchronizer" is set to 6(1 min), not
1 hour
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi,
We are using solr 7.7 cloud with CDCR(every collection has 3 replicas, 1
shard).
In solrconfig.xml,
tlog configuration is super simple like :
There is also daily data import and commit is called after data import every
time.
Indexing works fine, but the problem is that the number of
