Hello, I've recently set up a solr cloud using solr 6.0, and I've been having some trouble getting our collections to pick up schema updates. Following the docs on zkcli.sh <https://cwiki.apache.org/confluence/display/solr/Using+ZooKeeper+to+Manage+Configuration+Files> and the collections API <https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-api2>, I have uploaded the new schema by placing it onto a solr node at /opt/solr/server/configsets/my_collection/conf/schema.xml and running
β/opt/solr/cloud-scripts/zkcli.sh \ -zkhost zkdns.foo.bar \ -cmd upconfig \ -confname my_collection \ -confdir /opt/solr/server/configsets/my_collection/conf βand then triggering a reload of the collection by hitting solrNodeDns.foo.bar:<PORT>/solr/admin/collections?action=RELOAD&name=my_collection β The action reports success. Afterwards, however, I see something kind of strange. If I go to the admin page and look at the schema in / ~cloud?view=tree, β the updated schema is present. However, when I go to the collections admin page and click on schema, I do not see the new fields present. Querying for them directly also continues to lead to 400 "bad request" responses, so suggesting that the new schema hasn't been picked up anywhere else either. Is there another step that I am missing to complete the update? I found this stack overflow <http://stackoverflow.com/questions/36714077/solr-reload-is-not-picking-up-the-latest-changes-from-zookeeper> post where the posted is advised to recreate each core, though this seems like the wrong way to go to me. Any advice you have is appreciated. A few more notes about the cluster: I am running solr 6.0 in solr-cloud mode with freestanding zookeeper machines running zk 3.4.6. Thanks! Stephen stephen-lewis.net
