Hi Shawn, Thanks for the insight. As you've mentioned, renaming the core name in the core properties file does create unwanted consequences. I did give it a try in a test environment earlier. Renaming the core is not essential for us, it's just to add some convenience for a few folks using Solr UI to browse the data. It'll be good to have the documentation updated at some point to remove unsupported dthe core admin APIs.
Appreciate your help. Thanks, Shamik On Wed, Jun 8, 2022 at 4:21 PM Shawn Heisey <apa...@elyograg.org> wrote: > On 6/8/2022 5:06 PM, Shamik Bandopadhyay wrote: > > "msg": "Not supported in SolrCloud", > > Using the CoreAdmin API when running in cloud mode is a REALLY bad > idea. The CoreAdmin API cannot touch information in zookeeper. With > part of the information for a SolrCloud collection being in zookeeper > and part of it on the disk in the core.properties files, it causes > serious problems to try and use that API in cloud mode. > > Don't do it. Use the Collections API to make modifications to your > indexes. > > Looks like we made it explicitly not supported at some point in 8.x, and > I can tell you that is a decision that will NOT be reversed. We've seen > too many people break a working SolrCloud install completely by using > the CoreAdmin API to make changes. > > If you are absolutely certain that the change you are wanting to make > will not break the collection (and I am pretty sure that renaming a core > would break something) then you can manually modify the core.properties > file and restart Solr. You might also need to update the collection > information in zookeeper, which is why CoreAdmin has been disabled in > cloud mode. > > Thanks, > Shawn > >
