Pretty much what Webster and Erick mentioned, else please try the pdf I attached. I followed the official documentation doing that.
Amrit Sarkar Search Engineer Lucidworks, Inc. 415-589-9269 www.lucidworks.com Twitter http://twitter.com/lucidworks LinkedIn: https://www.linkedin.com/in/sarkaramrit2 On Thu, Sep 28, 2017 at 8:56 PM, Erick Erickson <erickerick...@gmail.com> wrote: > If Webster's idea doesn't solve it, the next thing to check is your > tlogs on the source cluster. If you have a successful connection to > the target and it's operative, the tlogs should be regularly pruned. > If not, they'll collect updates forever. > > Also, your Solr logs should show messages as CDCR does its work, to > you see any evidence that it's > 1> running > 2> sending docs? > > Also, your problem description doesn't provide any information other > than "it doesn't work", which makes it very hard to offer anything > except generalities, you might review: > > https://wiki.apache.org/solr/UsingMailingLists > > Best, > Erick > > > On Thu, Sep 28, 2017 at 7:47 AM, Webster Homer <webster.ho...@sial.com> > wrote: > > Check that you have autoCommit enabled in the target schema. > > > > Try sending a commit to the target collection. If you don't have > autoCommit > > enabled then the data could be replicating but not committed so not > > searchable > > > > On Thu, Sep 28, 2017 at 1:57 AM, Jiani Yang <jia...@umich.edu> wrote: > > > >> Hi, > >> > >> Recently I am trying to use CDCR to do the replication of my solr > cluster. > >> I have done exactly as what the tutorial says, the tutorial link is > shown > >> below: > >> https://lucene.apache.org/solr/guide/6_6/cross-data- > >> center-replication-cdcr.html > >> > >> But I cannot see any change on target data center even every status > looks > >> fine. I have been stuck in this situation for a week and could not find > a > >> way to resolve it, could you please help me? > >> > >> Please reply me ASAP! Thank you! > >> > >> Best, > >> Jiani > >> > > > > -- > > > > > > 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. >
