[
https://issues.apache.org/jira/browse/SOLR-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690289#comment-13690289
]
Shalin Shekhar Mangar commented on SOLR-4808:
---------------------------------------------
bq. For this mode, we should not allow preconfigured cores - so this shouldn't
happen - if it does for some weird reason, depending on your config, the node
should be removed shortly after by the overseer - I think the way you should
raise the number of replicas is to use the collections api to change the
replicationFactor.
Noble and I had a discussion about this. What you say is right but the problem
is about back-compat at least until the 4.x releases continue. In 5.0 we can
stop supporting collection creation via startup configuration. But until that
time we need to decide whether we throw an exception if a user starts up a
pre-configured core or treat replication factor as a minimum value and let the
core be added to the shard. After our discussion Noble and I were leaning
towards the latter option.
I have started to work on this. I'm going to create some issues around APIs to
modify replication factor and maxShardsPerNode. I also plan to store
replication factor (at a shard level only) and start using these values in
Overseer.
> Persist and use replication factor at Collection and Shard level
> ----------------------------------------------------------------
>
> Key: SOLR-4808
> URL: https://issues.apache.org/jira/browse/SOLR-4808
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Anshum Gupta
> Assignee: Shalin Shekhar Mangar
> Labels: solrcloud
>
> The replication factor for a collection as of now is not persisted and used
> while adding replicas.
> We should save the replication factor at collection factor as well as shard
> level.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
