You cannot just pick arbitrary parts of a JIRA discussion and expect them to work. JIRAs are places where discussion of alternatives takes place and the discussion often suggests ideas that are not incorporated in the final patch. The patch for the JIRA you mentioned, for instance, does not mention either of those parameters, which implies that they were simply part of the discussion and were never implemented.
So this sounds like an "XY" problem. You're asking why properties aren't persisted when you really want to take advantage of some functionality. What is that functionality? BTW, I'd go by the ref guide rather than JIRAs unless you examine the patch and see that the discussion was implemented in the patch. Best, Erick On Thu, Sep 8, 2016 at 9:33 PM, Swathi Singamsetty <swathisingamsett...@gmail.com> wrote: > Hi Team, > > To implement the feature "Persist and use the > replicationFactor,maxShardsPerNode at Collection&Shard level" am following > the steps mentioned in the jira ticket > https://issues.apache.org/jira/browse/SOLR-4808. > > I used the "smartCloud" and "autoManageCluster" properties to create a > collection in the create collection API to allow the overseer to bring up > the minimum no. of replicas for each shard as per the replicationFactor set > . But these 2 properties did not persist in the cluster state. Could > someone let me know how to use these properties in this feature? > > > > Thanks & Regards, > Swathi.
