I second Erick's recommendation, but just for the record legacyCloud was removed in (upcoming) Solr 9 and is still available in Solr 8.x. Most likely this explains Modassar why you found it in the documentation.
Ilan On Tue, Nov 3, 2020 at 5:11 PM Erick Erickson <erickerick...@gmail.com> wrote: > You absolutely need core.properties files. It’s just that they > should be considered an “implementation detail” that you > should rarely, if ever need to be aware of. > > Scripting manual creation of core.properties files in order > to define your collections has never been officially supported, it > just happened to work. > > Best, > Erick > > > On Nov 3, 2020, at 11:06 AM, Modassar Ather <modather1...@gmail.com> > wrote: > > > > Thanks Erick for your response. > > > > I will certainly use the APIs and not rely on the core.properties. I was > > going through the documentation on core.properties and found it to be > still > > there. > > I have all the solr install scripts based on older Solr versions and > wanted > > to re-use the same as the core.properties way is still available. > > > > So does this mean that we do not need core.properties anymore? > > How can we ensure that the core name is configurable and not dynamically > > set? > > > > I will try to use the APIs to create the collection as well as the cores. > > > > Best, > > Modassar > > > > On Tue, Nov 3, 2020 at 5:55 PM Erick Erickson <erickerick...@gmail.com> > > wrote: > > > >> You’re relying on legacyMode, which is no longer supported. In > >> older versions of Solr, if a core.properties file was found on disk Solr > >> attempted to create the replica (and collection) on the fly. This is no > >> longer true. > >> > >> > >> Why are you doing it this manually instead of using the collections API? > >> You can precisely place each replica with that API in a way that’ll > >> be continued to be supported going forward. > >> > >> This really sounds like an XY problem, what is the use-case you’re > >> trying to solve? > >> > >> Best, > >> Erick > >> > >>> On Nov 3, 2020, at 6:39 AM, Modassar Ather <modather1...@gmail.com> > >> wrote: > >>> > >>> Hi, > >>> > >>> I am migrating from Solr 6.5.1 to Solr 8.6.3. As a part of the entire > >>> upgrade I have the first task to install and configure the solr with > the > >>> core and collection. The solr is installed in SolrCloud mode. > >>> > >>> In Solr 6.5.1 I was using the following key values in core.properties > >> file. > >>> The configuration files were uploaded to zookeeper using the upconfig > >>> command. > >>> The core and collection was automatically created with the setting in > >>> core.properties files and the configSet uploaded in zookeeper and it > used > >>> to display on the Solr 6.5.1 dashboard. > >>> > >>> numShards=12 > >>> > >>> name=mycore > >>> > >>> collection=mycore > >>> > >>> configSet=mycore > >>> > >>> > >>> With the latest Solr 8.6.3 the same approach is not working. As per my > >>> understanding the core is identified using the location of > >> core.properties > >>> which is under *<SOLR_HOME>/mycore/core.properties.* > >>> > >>> Can you please help me with the following? > >>> > >>> > >>> - Is there any property I am missing to load the core and collection > as > >>> it used to be in Solr 6.5.1 with the help of core.properties and > >> config set > >>> on zookeeper? > >>> - The name of the core and collection should be configurable and not > >> the > >>> dynamically generated names. How can I control that in the latest > Solr? > >>> - Is the core and collection API the only way to create core and > >>> collection as I see that the core is also not getting listed even if > >> the > >>> core.properties file is present? > >>> > >>> Please note that I will be doing a full indexing once the setup is > done. > >>> > >>> Kindly help me with your suggestions. > >>> > >>> Best, > >>> Modassar > >> > >> > >
