this is consistent with the data disappearing from Zookeeper due
to misconfiguration and/or some external process removing it when
you reboot.
So here’s what I’d do next:
Go ahead and reboot. You do _not_ need to start Solr to run bin/solr
scripts, and among them are
bin/solr zk ls -r / -z
Hi Erick,
Here is the latest most error that I captured which seems to be actually
deleting the cores ( I did noticed that the core folders under the path
../solr/server/solr were deleted one by one when the server came back from
reboot)
2020-08-24 04:41:27.424 ERROR
Autopurge shouldn’t matter, that’s just cleaning up old snapshots. That is, it
should be configured, but having it enabled or not should have no bearing on
your data disappearing.
Also, are you absolutely certain that you are using your external ZK? Check the
port on the admin screen. 9983 is
Thanks Eric for looking into this..
But as I said before I confirmed that the paths in zookeeper were changed to
local path than the /tmp that comes default with package. Does the zoo.cfg need
to have autopurge settings ??which I don’t have in my config
Also I did make sure that zoo.cfg inside
Sounds like you didn’t change Zookeeper data dir. Zookeeper defaults to putting
its data in /tmp/zookeeper, see the zookeeper config file. And, of course, when
you reboot it goes away.
I’ve always disliked this, but the Zookeeper folks did it that way. So if you
just copy zoo_sample.cfg to
Can someone help me on the below issue??
I have configured solr 8.2 with one zookeeper 3.4 and 3 solr nodes
All the configs were pushed initially and Also Indexed all the data into
multiple collections with 3 replicas on each collection
Now part of server maintenance these solr nodes were
