[
https://issues.apache.org/jira/browse/SOLR-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398942#comment-13398942
]
Mark Miller commented on SOLR-3488:
-----------------------------------
bq. so basically, if I understood correctly, is that the overseer has the
capability of doing periodic checks without an explicit action / request from a
client which can help on cleaning states / check for failures / etc.
Yeah - basically, either every n seconds, or when the overseer sees a new node
come or go, it looks at each collection, checks its replication factor, and
either adds or removes nodes to match it given the nodes that are currently up.
So with some lag, whatever you set for the replication will eventually be
matched no matter the failures or random state of the cluster when the
collection is created or its replication factor changed.
> Create a Collections API for SolrCloud
> --------------------------------------
>
> Key: SOLR-3488
> URL: https://issues.apache.org/jira/browse/SOLR-3488
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Attachments: SOLR-3488.patch, SOLR-3488.patch, SOLR-3488.patch,
> SOLR-3488_2.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
