On 1/10/2016 2:29 AM, Allan Kamau 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
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 keepin
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
wrote:
> Did you by any chance start the first-time with bin/solr start -e
>
> An
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:2
What do you mean by cores getting deleted? Files created on filesystem for
these cores disappear?
How are you starting and stopping solr? Is this solr cloud or standalone
mode?
On Sun, Jan 10, 2016 at 2:59 PM, Allan Kamau wrote:
> We are able to load several cores into Solr 5.3.1.
> The problem
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 ena
