Are you sure you are reloading all the shards after the config change? You can also use the Collection Reload API to do this easily [1]. Are there any exceptions in the logs after a reload?
[1] - https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-ReloadaCollection On Mon, Nov 18, 2013 at 1:23 PM, vicky desai <vicky.de...@germinait.com> wrote: > Hi, > > I have a solr set up using external zookeeper . Whenever there are any > schema changes to be made I make those changes and upload the new config via > cloud-scripts. I then reload the core using the action > http://localhost:8190/solr/admin/cores?action=RELOAD&core=coreName > > Everything works fine after this. The new changes are reflected and core is > up for reading and writing. However when I go to the cloud view of solr it > shows the core name in orange which means the core is down. > > Can anybody help me in resolving the issue > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-cloud-view-shows-core-as-down-after-using-reload-action-tp4101625.html > Sent from the Solr - User mailing list archive at Nabble.com. -- Regards, Shalin Shekhar Mangar.
