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
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/guid
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
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.linkedi
