[ https://issues.apache.org/jira/browse/SOLR-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141182#comment-13141182 ]
Mark Miller commented on SOLR-2723: ----------------------------------- This is currently implemented with a very simple collection lock - since we are likely going to have an overseer, we should likely move from this impl to having the overseer assign. > If you don't choose a shard name for a SolrCore, the system should auto > assign shard names. > ------------------------------------------------------------------------------------------- > > Key: SOLR-2723 > URL: https://issues.apache.org/jira/browse/SOLR-2723 > Project: Solr > Issue Type: New Feature > Components: SolrCloud > Reporter: Mark Miller > Assignee: Mark Miller > Fix For: 4.0 > > > When you first boot up a node with the collection files to use, you might > also pass how many slices you want - if you choose 3 slices, the first 3 > nodes that come up would each go to a different slice and get a unique shard > name - further nodes that come up would be replicas in each slice and get one > of the 3 shard names. -- 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