Core admin is required for REQUESTRECOVERY. Otherwise, I agree, don’t use it.
wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Apr 28, 2019, at 4:14 PM, Erick Erickson <erickerick...@gmail.com> wrote: > > What Shawn said. Stop using the core admin API. It will not register the core > with ZooKeeper. legacyCloud=true may put the info in ZooKeeper, but usually > puts it in clusterstate.json rather than the proper place, > collections>>your_collection>>state.json. There’s no guarantee whatsoever > that legacyCloud will be supported in any fashion whatsoever in the future. > > No, more strongly than that. There is a _guarantee_ that legacyCloud will > _not_ be supported in the future, it’s just a matter of when. > > You are using unsupported functionality and are on your own. > > The collections API is here: > https://lucene.apache.org/solr/guide/7_3/collections-api.html > > Best, > Erick > >> On Apr 28, 2019, at 10:02 AM, Shawn Heisey <apa...@elyograg.org> wrote: >> >> On 4/28/2019 6:39 AM, ramyogi wrote: >>> Thanks Eric, After we create a collection and copy the index from one place >>> new place, we are doing UNLOAD core and CREATE core as below, is it wrong >>> and we have alternative to do that ? >> >> Do not use CoreAdmin when running SolrCloud. At all. It will cause you >> problems. All actions in SolrCloud need to happen through the Collections >> API. >> >> After you copy the index into place, simply reload the collection. Use the >> Collections API, not CoreAdmin. >> >> https://lucene.apache.org/solr/guide/7_7/collections-api.html#reload >> >> Thanks, >> Shawn >
