Hi Erick,

thanks for the hint. Indeed, i just forgot to paste the <updateLog> 
</updateLog> section into the email. It was configured just the same way as you 
wrote. Do you have any idea what else could be the cause for the error?

Best regard,

Gero

-----Original Message-----
From: Erick Erickson [mailto:erickerick...@gmail.com] 
Sent: Wednesday, November 23, 2016 5:00 PM
To: solr-user <solr-user@lucene.apache.org>
Subject: Re: Problem with Cross Data Center Replication

Your _source_ (i.e. cdcr_testa) doesn't have the CDCR update log configured.
This section isn't in solrconfig for cdcr_testa:

<updateHandler class="solr.DirectUpdateHandler2">
<updateLog class="solr.CdcrUpdateLog">
<str name="dir">${solr.ulog.dir:}</str>
<!--Any parameters from the original <updateLog> section --> </updateLog> 
</updateHandler>

The update log is the transfer mechanism between the source and target 
clusters, so it needs to be configured in both.

Best,
Erick.

P.S. kudos for including enough info to diagnose (assuming I'm right)!


On Wed, Nov 23, 2016 at 4:40 AM, WILLMES Gero (SAFRAN IDENTITY AND
SECURITY) <gero.will...@safrangroup.com> wrote:
> Hi Solr users,
>
> i try to configure Cross Data Center Replication according to 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62687
> 462
>
> I set up two independent solr clouds. I created the collection "cdcr_testa" 
> on the source cloud and the collection "backup_collection" on the target 
> cloud.
>
> I adapted the configurations, according to the documentation.
>
> solrconfig.xml of the collection "cdcr_testa" in the source cluster:
>
>    <requestHandler name="/cdcr" class="solr.CdcrRequestHandler">
>   <lst name="replica">
>     <str name="zkHost">127.0.0.2:2181</str>
>     <str name="source">cdcr_testa</str>
>     <str name="target">backup_collection</str>
>   </lst>
>
>   <lst name="replicator">
>     <str name="threadPoolSize">8</str>
>     <str name="schedule">1000</str>
>     <str name="batchSize">128</str>
>   </lst>
>
>   <lst name="updateLogSynchronizer">
>     <str name="schedule">1000</str>
>   </lst>
> </requestHandler>
>
>
> solrconfig.xml of the collection "backup_collection" in the target cluster:
>
> <requestHandler name="/cdcr" class="solr.CdcrRequestHandler">
>   <lst name="buffer">
>     <str name="defaultState">disabled</str>
>   </lst>
> </requestHandler>
>
> <requestHandler name="/update" class="solr.UpdateRequestHandler">
>   <lst name="defaults">
>     <str name="update.chain">cdcr-processor-chain</str>
>   </lst>
> </requestHandler>
>
> <updateRequestProcessorChain name="cdcr-processor-chain">
>   <processor class="solr.CdcrUpdateProcessorFactory"/>
>   <processor class="solr.RunUpdateProcessorFactory"/>
> </updateRequestProcessorChain>
>
> <!-- Modify the <updateLog> section of your existing <updateHandler> in your
>     config as below -->
> <updateHandler class="solr.DirectUpdateHandler2">
>   <updateLog class="solr.CdcrUpdateLog">
>     <str name="dir">${solr.ulog.dir:}</str>
>     <!--Any parameters from the original <updateLog> section -->
>   </updateLog>
> </updateHandler>
>
>
> When I now reload the collection "cdcr_testa", I allways get the 
> following  Solr Exception
>
> 2016-11-23 12:05:35.604 ERROR (qtp1134712904-8045) [c:cdcr_testa s:shard1 
> r:core_node1 x:cdcr_testa_shard1_replica1] o.a.s.s.HttpSolrCall 
> null:org.apache.solr.common.SolrException: Error handling 'reload' action
>         at 
> org.apache.solr.handler.admin.CoreAdminOperation$3.call(CoreAdminOperation.java:150)
>         at 
> org.apache.solr.handler.admin.CoreAdminHandler$CallInfo.call(CoreAdminHandler.java:367)
>         at 
> org.apache.solr.handler.admin.CoreAdminHandler.handleRequestBody(CoreAdminHandler.java:158)
>         at 
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:156)
>         at 
> org.apache.solr.servlet.HttpSolrCall.handleAdminRequest(HttpSolrCall.java:663)
>         at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:445)
>         at 
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:257)
>         at 
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:208)
>         at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
>         at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
>         at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>         at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>         at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>         at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1160)
>         at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
>         at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>         at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092)
>         at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>         at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>         at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
>         at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>         at org.eclipse.jetty.server.Server.handle(Server.java:518)
>         at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308)
>         at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244)
>         at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
>         at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
>         at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
>         at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246)
>         at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156)
>         at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
>         at 
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
>         at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.solr.common.SolrException: Unable to reload core 
> [cdcr_testa_shard1_replica1]
>         at org.apache.solr.core.CoreContainer.reload(CoreContainer.java:920)
>         at 
> org.apache.solr.handler.admin.CoreAdminOperation$3.call(CoreAdminOperation.java:148)
>         ... 31 more
> Caused by: org.apache.solr.common.SolrException: Solr instance is not 
> configured with the cdcr update log.
>         at org.apache.solr.core.SolrCore.<init>(SolrCore.java:773)
>         at org.apache.solr.core.SolrCore.reload(SolrCore.java:462)
>         at org.apache.solr.core.CoreContainer.reload(CoreContainer.java:914)
>         ... 32 more
> Caused by: org.apache.solr.common.SolrException: Solr instance is not 
> configured with the cdcr update log.
>         at 
> org.apache.solr.handler.CdcrRequestHandler.inform(CdcrRequestHandler.java:223)
>         at 
> org.apache.solr.core.SolrResourceLoader.inform(SolrResourceLoader.java:675)
>         at org.apache.solr.core.SolrCore.<init>(SolrCore.java:753)
>         ... 34 more
>
> This exception occurs on every reload.
> Do you have any idea, what might be the cause of the problem?
>
> Best regards,
>
> Gero
>
> #
> " 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."
> #
#
" 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."
#

Reply via email to