Re: Bidirectional CDCR not working
Thanks, Nish. It turned out to be other issue. I had not restarted one of the node in the cluster which had become leader meanwhile. It is good to know though that there is malformed XML in the example. I will try to submit a document fix soon. On Thu, Mar 14, 2019 at 5:37 PM Nish Karve wrote: > Arnold, > > Have you copied the configuration from the Solr docs? The bi directional > cluster configuration (for cluster 1) has a malformed XML. It is missing > the closing tag for the updateLogSynchronizer under the request handler > configuration. > > Please disregard if you have already considered that in your configuration. > I had a lot of issues trying to figure out the issue when I realized that > it was a documentation error. > > Thanks > Nishant > > > On Thu, Mar 14, 2019, 2:54 PM Arnold Bronley wrote: > > > Configuration is almost identical for both clusters in terms of cdcr > except > > for zkHost parameter configuration. > > > > On Thu, Mar 14, 2019 at 3:45 PM Arnold Bronley > > wrote: > > > > > Exactly. I have it defined in both clusters. I am following the > > > instructions from here . > > > > > > https://lucene.apache.org/solr/guide/7_7/cdcr-config.html#bi-directional-updates > > > > > > On Thu, Mar 14, 2019 at 3:40 PM Amrit Sarkar > > > wrote: > > > > > >> Hi Arnold, > > >> > > >> You need "cdcr-processor-chain" definitions in solrconfig.xml on both > > >> clusters' collections. Both clusters need to act as source and target. > > >> > > >> 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 Fri, Mar 15, 2019 at 1:03 AM Arnold Bronley < > arnoldbron...@gmail.com > > > > > >> wrote: > > >> > > >> > Hi, > > >> > > > >> > I used unidirectional CDCR in SolrCloud (7.7.1) without any issues. > > But > > >> > after setting up bidirectional cdcr configuration, I am not able to > > >> index a > > >> > document. > > >> > > > >> > Following is the error that I am getting: > > >> > > > >> > Async exception during distributed update: Error from server at > > >> > http://host1:8983/solr/techproducts_shard2_replica_n6: Bad Request > > >> > request: > > >> > http://host1 > > >> > > > >> > > > >> > > > :8983/solr/techproducts_shard2_replica_n6/update?update.chain=cdcr-processor-chain=TOLEADER= > > >> > > > >> > > > http://host2:8983/solr/techproducts_shard1_replica_n1=javabin=2 > > >> > Remote error message: unknown UpdateRequestProcessorChain: > > >> > cdcr-processor-chain > > >> > > > >> > Do you know why I might be getting this error? > > >> > > > >> > > > > > >
Re: Bidirectional CDCR not working
Arnold, Have you copied the configuration from the Solr docs? The bi directional cluster configuration (for cluster 1) has a malformed XML. It is missing the closing tag for the updateLogSynchronizer under the request handler configuration. Please disregard if you have already considered that in your configuration. I had a lot of issues trying to figure out the issue when I realized that it was a documentation error. Thanks Nishant On Thu, Mar 14, 2019, 2:54 PM Arnold Bronley Configuration is almost identical for both clusters in terms of cdcr except > for zkHost parameter configuration. > > On Thu, Mar 14, 2019 at 3:45 PM Arnold Bronley > wrote: > > > Exactly. I have it defined in both clusters. I am following the > > instructions from here . > > > https://lucene.apache.org/solr/guide/7_7/cdcr-config.html#bi-directional-updates > > > > On Thu, Mar 14, 2019 at 3:40 PM Amrit Sarkar > > wrote: > > > >> Hi Arnold, > >> > >> You need "cdcr-processor-chain" definitions in solrconfig.xml on both > >> clusters' collections. Both clusters need to act as source and target. > >> > >> 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 Fri, Mar 15, 2019 at 1:03 AM Arnold Bronley > > >> wrote: > >> > >> > Hi, > >> > > >> > I used unidirectional CDCR in SolrCloud (7.7.1) without any issues. > But > >> > after setting up bidirectional cdcr configuration, I am not able to > >> index a > >> > document. > >> > > >> > Following is the error that I am getting: > >> > > >> > Async exception during distributed update: Error from server at > >> > http://host1:8983/solr/techproducts_shard2_replica_n6: Bad Request > >> > request: > >> > http://host1 > >> > > >> > > >> > :8983/solr/techproducts_shard2_replica_n6/update?update.chain=cdcr-processor-chain=TOLEADER= > >> > > >> > http://host2:8983/solr/techproducts_shard1_replica_n1=javabin=2 > >> > Remote error message: unknown UpdateRequestProcessorChain: > >> > cdcr-processor-chain > >> > > >> > Do you know why I might be getting this error? > >> > > >> > > >
Re: Bidirectional CDCR not working
Configuration is almost identical for both clusters in terms of cdcr except for zkHost parameter configuration. On Thu, Mar 14, 2019 at 3:45 PM Arnold Bronley wrote: > Exactly. I have it defined in both clusters. I am following the > instructions from here . > https://lucene.apache.org/solr/guide/7_7/cdcr-config.html#bi-directional-updates > > On Thu, Mar 14, 2019 at 3:40 PM Amrit Sarkar > wrote: > >> Hi Arnold, >> >> You need "cdcr-processor-chain" definitions in solrconfig.xml on both >> clusters' collections. Both clusters need to act as source and target. >> >> 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 Fri, Mar 15, 2019 at 1:03 AM Arnold Bronley >> wrote: >> >> > Hi, >> > >> > I used unidirectional CDCR in SolrCloud (7.7.1) without any issues. But >> > after setting up bidirectional cdcr configuration, I am not able to >> index a >> > document. >> > >> > Following is the error that I am getting: >> > >> > Async exception during distributed update: Error from server at >> > http://host1:8983/solr/techproducts_shard2_replica_n6: Bad Request >> > request: >> > http://host1 >> > >> > >> :8983/solr/techproducts_shard2_replica_n6/update?update.chain=cdcr-processor-chain=TOLEADER= >> > >> http://host2:8983/solr/techproducts_shard1_replica_n1=javabin=2 >> > Remote error message: unknown UpdateRequestProcessorChain: >> > cdcr-processor-chain >> > >> > Do you know why I might be getting this error? >> > >> >
Re: Bidirectional CDCR not working
Exactly. I have it defined in both clusters. I am following the instructions from here . https://lucene.apache.org/solr/guide/7_7/cdcr-config.html#bi-directional-updates On Thu, Mar 14, 2019 at 3:40 PM Amrit Sarkar wrote: > Hi Arnold, > > You need "cdcr-processor-chain" definitions in solrconfig.xml on both > clusters' collections. Both clusters need to act as source and target. > > 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 Fri, Mar 15, 2019 at 1:03 AM Arnold Bronley > wrote: > > > Hi, > > > > I used unidirectional CDCR in SolrCloud (7.7.1) without any issues. But > > after setting up bidirectional cdcr configuration, I am not able to > index a > > document. > > > > Following is the error that I am getting: > > > > Async exception during distributed update: Error from server at > > http://host1:8983/solr/techproducts_shard2_replica_n6: Bad Request > > request: > > http://host1 > > > > > :8983/solr/techproducts_shard2_replica_n6/update?update.chain=cdcr-processor-chain=TOLEADER= > > > http://host2:8983/solr/techproducts_shard1_replica_n1=javabin=2 > > Remote error message: unknown UpdateRequestProcessorChain: > > cdcr-processor-chain > > > > Do you know why I might be getting this error? > > >
Re: Bidirectional CDCR not working
Hi Arnold, You need "cdcr-processor-chain" definitions in solrconfig.xml on both clusters' collections. Both clusters need to act as source and target. 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 Fri, Mar 15, 2019 at 1:03 AM Arnold Bronley wrote: > Hi, > > I used unidirectional CDCR in SolrCloud (7.7.1) without any issues. But > after setting up bidirectional cdcr configuration, I am not able to index a > document. > > Following is the error that I am getting: > > Async exception during distributed update: Error from server at > http://host1:8983/solr/techproducts_shard2_replica_n6: Bad Request > request: > http://host1 > > :8983/solr/techproducts_shard2_replica_n6/update?update.chain=cdcr-processor-chain=TOLEADER= > http://host2:8983/solr/techproducts_shard1_replica_n1=javabin=2 > Remote error message: unknown UpdateRequestProcessorChain: > cdcr-processor-chain > > Do you know why I might be getting this error? >
Bidirectional CDCR not working
Hi, I used unidirectional CDCR in SolrCloud (7.7.1) without any issues. But after setting up bidirectional cdcr configuration, I am not able to index a document. Following is the error that I am getting: Async exception during distributed update: Error from server at http://host1:8983/solr/techproducts_shard2_replica_n6: Bad Request request: http://host1 :8983/solr/techproducts_shard2_replica_n6/update?update.chain=cdcr-processor-chain=TOLEADER= http://host2:8983/solr/techproducts_shard1_replica_n1=javabin=2 Remote error message: unknown UpdateRequestProcessorChain: cdcr-processor-chain Do you know why I might be getting this error?
