[
https://issues.apache.org/jira/browse/SOLR-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399117#comment-13399117
]
Sami Siren commented on SOLR-3488:
----------------------------------
bq. 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.
That sounds like a good goal. I think we need to have special handling for
situation where whole cluster/collection is bounced or some planned maintenance
is to be done.
Hdfs has this feature called safe mode that is enabled on startup (and can be
turned on at any point) and while in that mode replication of blocks is
prohibited. When certain percentage of blocks are availabe it moves away from
this mode. Something like that might work in solr context also - meaning no
shard reorg would happen until certain percentage of the shards are available
or solr is specifically told to leave this mode.
http://hadoop.apache.org/hdfs/docs/current/hdfs_user_guide.html#Safemode
> 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
