On 3/4/2014 1:44 PM, bbi123 wrote:
I am currently using SOLR 4.2 (non cloud mode). I see that most of the
changes made to the config files (solrconfig.xml, schema.xml, elevate.xml,
stopwords.txt etc..) gets updated when reloading the core.
Is there any particular change (in any of the config files) requires a
restart instead of reload for the changes to be reflected?
I am trying to come up with an automated deployment process which will just
do reload (instead of restart) after the files are deployed to corresponding
folders and I want to make sure that I don't miss anything.
I would guess that if you are changing things like what jars you want to
load, you have to restart. I don't know whether Solr's resource loader
can cope with lib changes on a reload. For myself, I would plan on a
restart even if it could deal with it.
Just about anything else that people normally tweak when fine-tuning
their config is probably fine with a core reload.Most schema changes do
require a reindex in addition to the reload/restart. I recall that I
once came across a config change that required a reindex, but I can't
remember what it is now. It's sensible to do a full restart and reindex
after you're all done with tweaking.
Some servlet containers support restarting entire web applications
without shutting down the container. I've heard that this is prone to
memory leaks, and the problems with leaks are not from Solr, they're
inherent in the restart mechanism.
Thanks,
Shawn
