The key here is whether you are connecting to the same Zookeeper, an internal or an external one. So if you use the -c option without providing a -z option, you use the embedded Zookeeper. If you later start with a -z option, that's a _different_ zookeeper.
And, btw, Zookeeper defaults to keeping its files in the /tmp directory on *nix systems, see this little jewel in the zoo.cfg file: # the directory where the snapshot is stored. # do not use /tmp for storage, /tmp here is just # example sakes. dataDir=/tmp/zookeeper So if you just copy zoo_sample.cfg to zoo.cfg you can start and run just fine... until you reboot your machine. And finally, we're assuming you're really talking SolrCloud but that's not certain because you talk about "cores". What _exactly_ are you doing to "load cores"? Details matter. If you're using SolrCloud, you should NOT be using the "Core API" (or core admin screen) to do anything if at all possible, use the "Collections API" instead. FWIW, Erick On Sun, Jan 10, 2016 at 5:24 AM, Allan Kamau <kamaual...@gmail.com> wrote: > Let me investigate once more how the cores we have in our deployment were > created and I will provide an update as well as a better problem > description. > > Allan. > > On Sun, Jan 10, 2016 at 3:14 PM, Alexandre Rafalovitch <arafa...@gmail.com> > wrote: > >> Did you by any chance start the first-time with bin/solr start -e >> >> And then bin/solr restart? >> >> In that case, the solr home was not set after restart and needs to be >> passed in manually. >> >> Or some other unexpected solr.home situation. >> >> Just poking in the dark here. >> >> Regards, >> Alex >> On 10 Jan 2016 8:29 pm, "Allan Kamau" <kamaual...@gmail.com> wrote: >> >> > We are able to load several cores into Solr 5.3.1. >> > The problem is that after a restart of the server, these cores seem to >> get >> > deleted. >> > Is there a way to make cores loaded in Solr 5.x survive a server restart. >> > Could there be a setting in solr.xml or perhaps the "core.properties" >> files >> > that would enable core(s) survivability in the event of server restart. >> > I have searched for a solution to this issue but found none, though I >> feel >> > that it has already been answered. >> > >> > >> > Solr version >> > 5.3.1 >> > >> > Java version >> > java version "1.8.0_60" >> > Java(TM) SE Runtime Environment (build 1.8.0_60-b27) >> > Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode) >> > >> > OS version >> > CentOS release 6.5 (Final) >> > >> > >> > >> > Allan. >> > >>
