Webster, I have patch uploaded to both Cdcr supporting Tlog: https://issues.apache.org/jira/browse/SOLR-12057 and core not getting failed while initializing for Pull type replicas: https://issues.apache.org/jira/browse/SOLR-12071 and awaiting feedback from open source community. The solution for pull type replicas can be designed better, apart from that, if this is urgent need for you, please apply the patches for your packages and probably give a shot. I will added extensive tests for both the use-cases.
Amrit Sarkar Search Engineer Lucidworks, Inc. 415-589-9269 www.lucidworks.com Twitter http://twitter.com/lucidworks LinkedIn: https://www.linkedin.com/in/sarkaramrit2 Medium: https://medium.com/@sarkaramrit2 On Thu, Apr 26, 2018 at 2:46 AM, Erick Erickson <erickerick...@gmail.com> wrote: > CDCR won't really ever make sense for PULL replicas since the PULL > replicas have no tlog and don't do any indexing and can't ever become > a leader seamlessly. > > As for plans to address TLOG replicas, patches are welcome if you have > a need. That's really how open source works, people add functionality > as they have use-cases they need to support and contribute them back. > So far this isn't a high-demand topic. > > Best, > Erick > > On Wed, Apr 25, 2018 at 8:03 AM, Webster Homer <webster.ho...@sial.com> > wrote: > > I was looking at SOLR-12057 > > > > According to the comment on the ticket, CDCR can not work when a > collection > > has PULL Replicas. That seems like a MAJOR limitation to CDCR and PULL > > Replicas. Is this likely to be addressed in the future? > > CDCR currently is broken for TLOG replicas too. > > > > https://issues.apache.org/jira/browse/SOLR-12057? > focusedCommentId=16391558&page=com.atlassian.jira. > plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16391558 > > > > Thanks > > > > -- > > > > > > 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 > > <http://www.emdgroup.com/disclaimer> to access the > > German, French, Spanish > > and Portuguese versions of this disclaimer. >
