Solr-Collection or Core not reloading schema.xml -


i using solar 4.6 , changed inside schema.xml. in order update schema.xml inside core used zkcli. works fine , able see modified schema.xml inside solr admin gui under cloud\tree\config\foobar\schema.xml.

but after calling

  • http://localhost:8983/solr/admin/collections?action=reload&name=foobar ,
  • http://localhost:8983/solr/admin/cores?action=reload&name=foobar,

the old schema.xml still in core named foobar.

your 2nd http request core api wrong. change name core:

http://localhost:8983/solr/admin/cores?action=reload&name=foobar should http://localhost:8983/solr/admin/cores?action=reload&core=foobar.


http://archive.apache.org/dist/lucene/solr/ref-guide/apache-solr-ref-guide-4.6.pdf (page 277)

reload

the reload action loads new core configuration of existing, registered solr core. while new core initializing, existing 1 continue handle requests. when new solr core ready, takes on , old core unloaded.

this useful when you've made changes solr core's configuration on disk, such adding new field definitions. calling reload action lets apply new configuration without having restart web container. core container not persist solrcloud solr.xml parameters, such solr/@zkhost , solr/cores/@hostport, ignored.

http://localhost:8983/solr/admin/cores?action=reload&core=core0

the reload action accepts single parameter, core, name of core reloaded.


see https://cwiki.apache.org/confluence/display/solr/coreadmin+api#coreadminapi-reload


Comments

Popular posts from this blog

apache - Remove .php and add trailing slash in url using htaccess not loading css -

javascript - jQuery show full size image on click -