Re: Three questions about huge tlog problem and CDCR

2019-12-20 Thread alwaysbluesky
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

Re: Three questions about huge tlog problem and CDCR

2019-12-19 Thread damienk
Did you run /cdcr?action=DISABLEBUFFER on both sides? On Fri, 20 Dec 2019 at 05:22, alwaysbluesky wrote: > 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?actio

Re: Three questions about huge tlog problem and CDCR

2019-12-19 Thread alwaysbluesky
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

Re: Three questions about huge tlog problem and CDCR

2019-12-19 Thread Erick Erickson
This usually indicates that the connection between DCs is broken and one or the other is falling behind. Note: “bidirectional” does _not_ mean that you can index to both DCs simultaneously, rather than you can switch from indexing in one DC to the other…. Best, Erick > On Dec 19, 2019, at 1:0

Re: Three questions about huge tlog problem and CDCR

2019-12-18 Thread alwaysbluesky
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