What this sounds like is you’re not really connecting to ZooKeeper the way you think. First, insure that you’re really connecting from Solr by going to the admin UI and looking at the Zookeeper information. Are the URLs and ports correct?
Second, Zookeeper by default puts the data in /tmp/zookeper, which will disappear upon reboot. Make very sure your ZK data dir points somewhere permanent in zoo.cfg. Third, there should be no reason to restart Zookeeper. Fourth, if you’re using an older version of Solr, lingering replicas would magically reappear. Look for “legacyCloud” in the reference guide for the version you’re using. If legacyCloud = true, any remnants of collections found on disk will magically reappear. the “smoking gun” here is if you have a clutserstate.json in Zookeeper that has some collection info, and the rest of your info in collections/<yourcollection>/state.json. Best, Erick > On Aug 18, 2020, at 1:32 PM, yaswanth kumar <yaswanth...@gmail.com> wrote: > > I am using solr with zookeeper ensemble, but some time when we delete the > collection with the solr API , they are getting disappeared from solr cloud > but after some days, when the machines are rebooted, they are coming back > on the cloud but with down status. Not really sure if its an issue > with zookeeper which is not persisting the delete activity on the > clusterstate (even clusterstate is showing back these nodes with down > status) > > Also the similar issue is happening when we update the schema , when we do > any modifications to solr schema and upload it via zookeeper it works fine > until the next reboot of the solr boxes, once the reboot is done, for some > reason its getting the back the older version schema. > > Is it mandatory that we need to restart zookeeper upon doing the above two > operations always?? > > -- > Thanks & Regards, > Yaswanth Kumar Konathala. > yaswanth...@gmail.com
