Will do. Thanks.
On Fri, Jun 20, 2025 at 3:46 PM Vincenzo D'Amore wrote:
> Solr Nodes and zookeeper nodes should see themselves. First try to solve
> the network problem.
> But I strongly suggest avoiding such configuration.
> I suggest have two different solr clusters insisting on different zoo
Could chroot be involved?
https://solr.apache.org/guide/solr/latest/deployment-guide/taking-solr-to-production.html#zookeeper-chroot
On Fri, Jun 20, 2025 at 12:12 PM Gummadi, Ramesh
wrote:
> Yes. We are using a SolrCLoud Cluster. The new solr nodes cannot see the
> old solr nodes. That might be
Solr Nodes and zookeeper nodes should see themselves. First try to solve
the network problem.
But I strongly suggest avoiding such configuration.
I suggest have two different solr clusters insisting on different zookeeper
ensembles (aka cluster)
If you need to keep the two clusters in sync there ar
Yes. We are using a SolrCLoud Cluster. The new solr nodes cannot see the
old solr nodes. That might be the issue. However all solr nodes can see the
zookeeper ensemble.
On Thu, Jun 19, 2025 at 8:53 PM Vincenzo D'Amore wrote:
> If I understand correctly you are trying to share a solr (cloud?) clu
If I understand correctly you are trying to share a solr (cloud?) cluster
between two different and remote data centers. As far as I know all the
nodes of a solr cluster should see themselves and all of them should see
the zookeeper ensemble. So we expect they are all in the same network. With
Solr
This is a bad idea. Set up each region independently.
> On Jun 19, 2025, at 9:23 AM, Gummadi, Ramesh
> wrote:
>
> We have a solr cluster in abc data center. A new collection needs to be
> created in qwe data center with the same config. There are 4 nodes running
> in qwe data center. The coll
