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 <rameshchandra.gumm...@ironmountain.com.invalid> wrote: > 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 <v.dam...@gmail.com> > wrote: > > > 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 > > SolrCloud clusters, when a solr node that receives a request can ask to > > another node to work for the response. I hope this helps to clarify why > you > > should have two separate clusters. So, are you using a SolrCloud cluster? > > > > Vincenzo D'Amore > > > > > > > > On Thu, 19 Jun 2025 at 15:23, Gummadi, Ramesh > > <rameshchandra.gumm...@ironmountain.com.invalid> 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 collection needs to be created with these 4 > > nodes. > > > The ports are open from this data center to the zookeepers in abc data > > > center. There is no connectivity between solr nodes in abc data center > > and > > > qwe data center. solr nodes are running in the qwe data center and are > > seen > > > in live_nodes of zookeeper in abc data center. > > > The collection is not getting created. Below is the error. > > > org.apache.solr.client.solrj.SolrServerException:IOException occurred > > when > > > talking to server at:Any ideas. > > > > > > -- > > > Ramesh Gummadi > > > > > > -- > > > The information contained in this email message and its attachments is > > > intended only for the private and confidential use of the recipient(s) > > > named above, unless the sender expressly agrees otherwise. Transmission > > of > > > email over the Internet is not a secure communications medium. If you > are > > > requesting or have requested the transmittal of personal data, as > defined > > > in applicable privacy laws by means of email or in an attachment to > > email, > > > you must select a more secure alternate means of transmittal that > > supports > > > your obligations to protect such personal data. > > > > > > If the reader of this > > > message is not the intended recipient and/or you have received this > email > > > in error, you must take no action based on the information in this > email > > > and you are hereby notified that any dissemination, misuse or copying > or > > > disclosure of this communication is strictly prohibited. If you have > > > received this communication in error, please notify us immediately by > > > email > > > and delete the original message. > > > > > > > -- > The information contained in this email message and its attachments is > intended only for the private and confidential use of the recipient(s) > named above, unless the sender expressly agrees otherwise. Transmission of > email over the Internet is not a secure communications medium. If you are > requesting or have requested the transmittal of personal data, as defined > in applicable privacy laws by means of email or in an attachment to email, > you must select a more secure alternate means of transmittal that supports > your obligations to protect such personal data. > > If the reader of this > message is not the intended recipient and/or you have received this email > in error, you must take no action based on the information in this email > and you are hereby notified that any dissemination, misuse or copying or > disclosure of this communication is strictly prohibited. If you have > received this communication in error, please notify us immediately by > email > and delete the original message. > -- Sincerely yours Mikhail Khludnev
