We have just upgraded our QA solr clouds to 7.2.0 We have 3 solr clouds. collections in the first cloud replicate to the other 2
For existing collections which we upgraded in place using the lucene index upgrade tool seem to behave correctly data written to collections in the first environment replicates to the other 2 We created a new collection has 2 shards each with 2 replicas. The new collection uses tlog replicas instead of NRT replicas. We configured CDCR similarly to other collections so that writes to the first are sent to the other 2 clouds. However, we never see data appear in the target collections. We do see tlog files appear, and I can see cdcr update messages in the logs, but none of the cores ever get any data in them. So the tlogs accumulate but are never loaded into the target collections This doesn't seem correct. I'm at a loss as to what to do next. We will probably copy the index files from the one collection to the other two collections directly, but shouldn't cdcr be sending the data? Does cdcr work with tlog replicas? -- 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.
