At present, CDCR does not work with HDFS. The update log implementation is
different and incompatible at the moment. Please open a jira issue to
support cdcr under hdfs -- patches are always welcome!
On Tue, Nov 29, 2016 at 8:36 PM, ZHOU Ran (SAFRAN IDENTITY AND SECURITY) <
ran.z...@safrangroup.com> wrote:
> Hello all,
>
>
>
> could someone help on this?
>
>
>
> Best Regards
>
> Ran
>
>
>
> *Von:* ZHOU Ran (SAFRAN IDENTITY AND SECURITY)
> *Gesendet:* Freitag, 25. November 2016 15:37
> *An:* 'solr-user@lucene.apache.org' <solr-user@lucene.apache.org>
> *Betreff:* Using Solr CDCR with HdfsDirectoryFactory
>
>
>
> Hello
>
>
>
>
>
> Hi All,
>
>
>
> I have followed the guide „Cross Data Center Replication (CDCR)“ and get
> my source collection replicated to the target. And then I tried to use HDFS
> as storage for both Solr clusters, but failed with the following error
> message:
>
>
>
> ERROR: Failed to create collection 'collection11' due to:
> {192.168.5.95:8983_solr=org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:Error
> from server at http://192.168.5.95:8983/solr: Error CREATEing SolrCore
> 'collection11_shard1_replica1': Unable to create core
> [collection11_shard1_replica1] Caused by: Solr instance is not configured
> with the cdcr update log.}
>
>
>
> Actually Solr with HDFS works for me. In the configuration for CDCR, there
> is one block:
>
>
>
> <updateHandler class="solr.DirectUpdateHandler2">
>
> <updateLog class="solr.CdcrUpdateLog">
>
> <str name="dir">${solr.ulog.dir:}</str>
>
> <!--Any parameters from the original <updateLog> section -->
>
> </updateLog>
>
> </updateHandler>
>
>
>
>
>
> And I know that if HdfsDirectoryFactory is used, then updateHandler will
> initialized updateLog with the class HdfsUpdateLog. Is this the problem
> that CDCR does not work with HDFS? Since the updateLog cannot be
> initialized with CdcrUpdateLog?
>
>
>
> Thanks in advance for your help!
>
>
>
> Best Regards
>
>
>
> *Ran ZHOU*
> Software Engineer
>
>
> *T* +49 (0) 234 97 87 59 <+49%20234%20978759>
>
> *E* ran.z...@safrangroup.com *NEW*
>
>
>
> L-1 Identity Solutions AG
>
> Universitätsstrasse 160 I 44801 BOCHUM - GERMANY
> *www.safran-identity-security.com*
> <http://www.safran-identity-security.com/?utm_source=signmail&utm_medium=mailpro&utm_campaign=signmailEN>
>
>
> <http://www.safran-identity-security.com/en/stay-in-touch-with-us?utm_source=subscribemail&utm_medium=mailpro&utm_campaign=subscribemailE>
> <http://www.safran-identity-security.com/en/stay-in-touch-with-us?utm_source=subscribemail&utm_medium=mailpro&utm_campaign=subscribemailE>
>
> <https://twitter.com/SafranIDSec>
>
> <https://www.youtube.com/user/SafranMorpho>
>
> <https://www.linkedin.com/company/safran-identity-&-security/>
>
>
>
>
> *Managing Board:* Dr. Martin Werner (Vors. / Chairman) I Christèle Jacqz
> I Francois Rieul* Supervisory Board: *Jean-Christophe Fondeur (Vors. /
> Chairman)
>
> *Register Court:* Amtsgericht Bochum I HRB 69 54 | *UST-ID / VAT ID:* DE
> 813124378
>
>
>
> #
> " Ce courriel et les documents qui lui sont joints peuvent contenir des
> informations confidentielles, être soumis aux règlementations relatives au
> contrôle des exportations ou ayant un caractère privé. S'ils ne vous sont
> pas destinés, nous vous signalons qu'il est strictement interdit de les
> divulguer, de les reproduire ou d'en utiliser de quelque manière que ce
> soit le contenu. Toute exportation ou réexportation non autorisée est
> interdite.Si ce message vous a été transmis par erreur, merci d'en informer
> l'expéditeur et de supprimer immédiatement de votre système informatique ce
> courriel ainsi que tous les documents qui y sont attachés."
> ******
> " This e-mail and any attached documents may contain confidential or
> proprietary information and may be subject to export control laws and
> regulations. If you are not the intended recipient, you are notified that
> any dissemination, copying of this e-mail and any attachments thereto or
> use of their contents by any means whatsoever is strictly prohibited.
> Unauthorized export or re-export is prohibited. If you have received this
> e-mail in error, please advise the sender immediately and delete this
> e-mail and all attached documents from your computer system."
> #
>
--
Regards,
Shalin Shekhar Mangar.
