If you just deleted the tlog files on the source, you'd likely miss updates, right? I can think of two ways to get source and target back in sync:
1> go ahead and delete the tlogs, then re-index from some point guaranteed to have been propagated to the target _before_ the tlog went wonky. 2> rebuild the target collection as though you were just starting CDCR on an existing collection like the "initial startup" here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62687462#CrossDataCenterReplication(CDCR)-InitialStartup Best, Erick On Fri, Jan 6, 2017 at 9:09 AM, Webster Homer <webster.ho...@sial.com> wrote: > We recently had a problem where the solr transaction log became corrupted > during a data load. The collection was a CDCR source and we started seeing > problems on both source and target. > > This happened while testing and was not in a production system. So we just > deleted both collections and recreated them after fixing the root cause. > > If this had been a production system that would not have been acceptable. > > What is the best way to recover from a problem like this? Stop cdcr and > delete the tlog files? > > -- > > > This message and any attachment are confidential and may be privileged or > otherwise protected from disclosure. If you are not the intended recipient, > you must not copy this message or attachment or disclose the contents to > any other person. If you have received this transmission in error, please > notify the sender immediately and delete the message and any attachment > from your system. Merck KGaA, Darmstadt, Germany and any of its > subsidiaries do not accept liability for any omissions or errors in this > message which may arise as a result of E-Mail-transmission or for damages > resulting from any unauthorized changes of the content of this message and > any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its > subsidiaries do not guarantee that this message is free of viruses and does > not accept liability for any damages caused by any virus transmitted > therewith. > > Click http://www.emdgroup.com/disclaimer to access the German, French, > Spanish and Portuguese versions of this disclaimer.
