[ 
https://issues.apache.org/jira/browse/SOLR-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690274#comment-13690274
 ] 

Mark Miller commented on SOLR-4808:
-----------------------------------

{quote}We need to redefine replicationFactor as the minimum no:of replicas for 
a given shard. The cluster will have atleast those many no:of replicas for that 
given shard. If the number falls below , that the overseer should attempt to 
bring the number upto that.{quote}

I don't think it needs to necessarily be redefined - you are specifying the 
replicationFactor you would like, not the minimum replicationFactor you'd like.

bq. If the number falls below , that the overseer should attempt to bring the 
number upto that.

I think any auto cluster changes should be optional - by default we should not 
meddle. And one of those options should allow trying to reduce to the right 
replicationFactor if you have too many the same way you might raise to it.

bq. What if a node is asked to join a shard which has enough replicas according 
to the replicationFactor?

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.

Or don't use this mode where the Overseer keeps things in line and it's up to 
you to manually do what you want.
                
> 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]

Reply via email to