Re: Turn off CDCR for only selected target clusters
@Shawn: You are right. In my case, the collection name is same as
configuration name and that is why it works. Do you know if there is some
other property that I can use that refers to the collection name instead?
On Wed, Aug 28, 2019 at 3:52 PM Shawn Heisey wrote:
> On 8/28/2019 1:42 PM, Arnold Bronley wrote:
> > I have configured the SolrCloud collection-wise only and there is no
> other
> > way. The way you have defined 3 zkHosts (comma separated values for
> zkHost
> > property), I tried that one before as it was more intuitive. But it did
> not
> > work for me. I had to use 3 different replica elements each for one of
> the
> > 3 SolrCloud clusters. source and target properties mention the same
> > collection name in my case. Instead of hardcoding it, I am using the
> > collection.configName variable which gets replaced by the collection name
> > to which this solrconfig.xml belongs to.
>
> I am pretty sure that ${collection.configName} refers to the
> configuration name stored in zookeeper, NOT the collection name. There
> is nothing at all in Solr that requires those names to be the same, and
> for many SolrCloud installs, they are not the same. If this is working
> for you, then you're probably naming your configs the same as the
> collection. If you were to ever use the same config on multiple
> collections, that would probably stop working.
>
> I do not know if there is a property with the collection name. There
> probably is.
>
> Thanks,
> Shawn
>
Re: Turn off CDCR for only selected target clusters
On 8/28/2019 1:42 PM, Arnold Bronley wrote:
I have configured the SolrCloud collection-wise only and there is no other
way. The way you have defined 3 zkHosts (comma separated values for zkHost
property), I tried that one before as it was more intuitive. But it did not
work for me. I had to use 3 different replica elements each for one of the
3 SolrCloud clusters. source and target properties mention the same
collection name in my case. Instead of hardcoding it, I am using the
collection.configName variable which gets replaced by the collection name
to which this solrconfig.xml belongs to.
I am pretty sure that ${collection.configName} refers to the
configuration name stored in zookeeper, NOT the collection name. There
is nothing at all in Solr that requires those names to be the same, and
for many SolrCloud installs, they are not the same. If this is working
for you, then you're probably naming your configs the same as the
collection. If you were to ever use the same config on multiple
collections, that would probably stop working.
I do not know if there is a property with the collection name. There
probably is.
Thanks,
Shawn
Re: Turn off CDCR for only selected target clusters
Hi Erick,
I have configured the SolrCloud collection-wise only and there is no other
way. The way you have defined 3 zkHosts (comma separated values for zkHost
property), I tried that one before as it was more intuitive. But it did not
work for me. I had to use 3 different replica elements each for one of the
3 SolrCloud clusters. source and target properties mention the same
collection name in my case. Instead of hardcoding it, I am using the
collection.configName variable which gets replaced by the collection name
to which this solrconfig.xml belongs to.
If follow your configuration (which does not work in my case and I have
tested it), my question was how to NOT send CDCR updates to targetZkHost2
and targetZkHost3 but not targetZkHost1?
On Tue, Aug 13, 2019 at 3:23 PM Erick Erickson
wrote:
> You configure CDCR by _collection_, so this question really makes no
> sense.
> You’d never mention collection.configName. So what I suspect is that you’re
> misreading the docs.
>
>
> ${targetZkHost1},${targetZkHost2},${targetZkHost3}
> sourceCollection_on_local_cluster
> targetCollection_on_targetZkHost1 2 and 3
>
>
> “Turning off CDCR” selective for ZooKeeper instances really makes no sense
> as the
> point of ZK ensembles is to keep running even if one goes away.
>
> So can you rephrase the question? Or state the problem you’re trying to
> solve another way?
>
> Best,
> Erick
>
> > On Aug 13, 2019, at 1:57 PM, Arnold Bronley
> wrote:
> >
> > Hi,
> >
> > Is there a way to turn off the CDCR for only selected target clusters.
> >
> > Say, I have a configuration like following. I have 3 target clusters
> > targetZkHost1, targetZkHost2 and targetZkHost3. Is it possible to turn
> off
> > the CDCR for targetZkHost2 and targetZkHost3 but keep it on for
> > targetZkHost1?
> >
> > E.g.
> >
> >
> >
> > ${targetZkHost1}
> > ${collection.configName}
> > ${collection.configName}
> >
> >
> >
> > ${targetZkHost2}
> > ${collection.configName}
> > ${collection.configName}
> >
> >
> >
> > ${targetZkHost3}
> > ${collection.configName}
> > ${collection.configName}
> >
> >
> >
> > 8
> > 1000
> > 128
> >
> >
> >
> > 1000
> >
> >
> >
> > disabled
> >
> >
>
>
Re: Turn off CDCR for only selected target clusters
You configure CDCR by _collection_, so this question really makes no sense.
You’d never mention collection.configName. So what I suspect is that you’re
misreading the docs.
${targetZkHost1},${targetZkHost2},${targetZkHost3}
sourceCollection_on_local_cluster
targetCollection_on_targetZkHost1 2 and 3
“Turning off CDCR” selective for ZooKeeper instances really makes no sense as
the
point of ZK ensembles is to keep running even if one goes away.
So can you rephrase the question? Or state the problem you’re trying to solve
another way?
Best,
Erick
> On Aug 13, 2019, at 1:57 PM, Arnold Bronley wrote:
>
> Hi,
>
> Is there a way to turn off the CDCR for only selected target clusters.
>
> Say, I have a configuration like following. I have 3 target clusters
> targetZkHost1, targetZkHost2 and targetZkHost3. Is it possible to turn off
> the CDCR for targetZkHost2 and targetZkHost3 but keep it on for
> targetZkHost1?
>
> E.g.
>
>
>
> ${targetZkHost1}
> ${collection.configName}
> ${collection.configName}
>
>
>
> ${targetZkHost2}
> ${collection.configName}
> ${collection.configName}
>
>
>
> ${targetZkHost3}
> ${collection.configName}
> ${collection.configName}
>
>
>
> 8
> 1000
> 128
>
>
>
> 1000
>
>
>
> disabled
>
>
Turn off CDCR for only selected target clusters
Hi,
Is there a way to turn off the CDCR for only selected target clusters.
Say, I have a configuration like following. I have 3 target clusters
targetZkHost1, targetZkHost2 and targetZkHost3. Is it possible to turn off
the CDCR for targetZkHost2 and targetZkHost3 but keep it on for
targetZkHost1?
E.g.
${targetZkHost1}
${collection.configName}
${collection.configName}
${targetZkHost2}
${collection.configName}
${collection.configName}
${targetZkHost3}
${collection.configName}
${collection.configName}
8
1000
128
1000
disabled
