[
https://issues.apache.org/jira/browse/SOLR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573647#comment-13573647
]
Michael Della Bitta commented on SOLR-4409:
-------------------------------------------
OK, understood, thanks!
> Collection creation should succeed if number of shards == number of nodes,
> regardless of replicationFactor.
> -----------------------------------------------------------------------------------------------------------
>
> Key: SOLR-4409
> URL: https://issues.apache.org/jira/browse/SOLR-4409
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.1
> Environment: 3 node SolrCloud using 4.1 and Tomcat 7, external 3 node
> zookeeper, running in AWS.
> Reporter: Michael Della Bitta
> Priority: Minor
>
> I was expecting that manually calling the Collections API to create a
> collection with the replicationFactor set to a value higher than
> numShards/number of nodes would create the collection with no replicants and
> cap the overall possible number of replicants when the cluster grows larger.
> Instead I received this message:
> "SEVERE: Cannot create collection $foo. Value of maxShardsPerNode is 1, and
> the number of live nodes is 3. This allows a maximum of 3 to be created.
> Value of numShards is 3 and value of replicationFactor is 2. This requires 6
> shards to be created (higher than the allowed number)"
> Not sure what the thinking behind this is, and maybe I'm just not getting it,
> but I would assume collection creation would succeed if the collection is a
> valid collection.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
