Hi Shawn, Thanks for the reply. We upgraded zookeeper from 3.4.8 to 3.6.2. We did code changes too, and mostly converted the solr server Calls to httpsolrclient calls. This exception occurs only in the standalone setup, in cluster setup it still works fine.
Thanks Reej Sent from my iPhone > On 7 Jun 2021, at 11:58 AM, Shawn Heisey <apa...@elyograg.org> wrote: > > On 6/6/2021 8:35 AM, Reej Nayagam wrote: >>> This was working in both cluster and standalone setups earlier in >>> solr4.10.2 but in 8.8.2 was it not working. Kindly advise. >>> This code is to fetch the cores and update our database from solr. >>> I’m getting throw exception “couldn’t connect to zookeeper for cluster”. >>> Followed by keeperexception keeper error code =session expired for >>> /aliases.json and /clusterstate.json >>> >>> Kindly advise if we need to do a code change if it’s standalone setup or >>> it’s a network latency or GC pause issue as mentioned in some >>> Online reference. > > In Solr 4.x, the ZK version would have been 3.4.x ... but in 8.x, it is a lot > newer. I don't know whether it's 3.5.x or 3.6.x. > > When we upgraded to 3.5.x, extensive code changes in Solr were required. > Your software probably also requires code changes. > > You won't find anything in /clusterstate.json in modern Solr versions ... the > file still exists in the ZK database, but is empty. The actual state is now > located in state.json files under the collection definition. > > We are not going to know how to solve KeeperException problems. That is > coming from ZooKeeper code, not Solr code. You'll probably need to enlist > the help of the ZK project. > > Thanks, > Shawn
