[SOLR-4120] Collection API: Support for specifying a list of solrs to spread a new collection across

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.0
• Fix Version/s: 4.1, 6.0
• Component/s: multicore, SolrCloud
• Labels: collection-api multicore shard shard-allocation
• Assignee: Mark Miller
• Reporter: Per Steffensen
• Created: 28/Nov/12 19:10
• Updated: 09/May/16 18:53
• Resolved: 14/Dec/12 18:16

Description

When creating a new collection through the Collection API, the Overseer (handling the creation) will spread shards for this new collection across all live nodes.

Sometimes you dont want a collection spread across all available nodes. Allow for the create operation of the Collection API, to take a createNodeSet parameter containing a list of Solr to spread the new shards across. If not provided it will just spread across all available nodes (default).

For an example of a concrete case of usage see: https://issues.apache.org/jira/browse/SOLR-4114?focusedCommentId=13505506&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13505506

Issue Links

• relates to: SOLR-4114 Collection API: Allow multiple shards from one collection on the same Solr server