There’s some documentation in the ref guide, did you see it? Basically, if a replica is discovered by a solr instance by finding a “core.properties” file under SOLR_HOME, legacyCloud=true will try to reconstruct the ZooKeeper entry if it’s not there. This lead to lots of issues, and so it has been deprecated and should not be enabled.
It should not affect collection _creation_ unless you’re manually creating directories under SOLR_HOME and/or using the core (NOT collection) admin API to create replicas, which you also should not do. IOW, the collection admin API CREATE should not be sensitive at all to this setting. Use the collections ADDREPLICA API to add replicas and you should be set. You can even create a collection with the special EMPTY nodeset that will allow you to precisely place each and every replica where you want it. Best, Erick > On Apr 24, 2019, at 9:29 AM, ramyogi <ramy...@gmail.com> wrote: > > What is legacyCloud properties does. Is there a document I could refer. Why > it impacts collection creation with rule based and index copy from one to > another. Replicas not registered how to fix without legacyCloud=true > settings. > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
