The behavior has changed from Solr 5.0 onwards
Please refer to the How does it work section here
https://cwiki.apache.org/confluence/display/solr/Config+API
TL:DR
* Every node watches the conf set directory it is using
* Updating individual files WILL NOT trigger a config reload. BUt if you
On 4/5/2015 12:32 AM, Shai Erera wrote:
So, the questions that I have are:
1. It does look like Solr re-loads cores on configuration changes, is
that true?
2. If (1) is YES, do I still need to manually invoke a collection RELOAD
explicitly after updating the configuration?
it.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Unable-to-update-config-file-using-zkcli-or-RELOAD-tp4197376p4197494.html
Sent from the Solr - User mailing list archive at Nabble.com.
/solrhome/ -confdir /mnt/opt/solrhome/solr/collection1/conf/
2. Use the same node to run the RELOAD
http://54.151.xx.xxx:8983/solr/admin/cores?action=RELOADcore=collection1
--
View this message in context:
http://lucene.472066.n3.nabble.com/Unable-to-update-config-file-using-zkcli-or-RELOAD
On 4/3/2015 12:28 AM, shamik wrote:
Ok, I figured the steps in case someone needs a reference. It required both
zkcli and RELOAD to update the changes.
1. Use zkcli to load the changes. I ran it from the node which used the
bootstrapping.
sh zkcli.sh -cmd upconfig -zkhost zoohost1:2181
Thanks Shawn for the pointer, really appreciate it.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Unable-to-update-config-file-using-zkcli-or-RELOAD-tp4197376p4197494.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi,
I'm facing a weird issue. I've a solr cloud cluster with 2 shards having
a replica each. I started the cluster
using -Dbootstrap_confdir=./solr/collection1/conf
-Dcollection.configName=myconf. After the cluster is up and running, I
added a new request handler (newhandler) and wanted to push
