[SOLR-11990] Make it possible to co-locate replicas of multiple collections together in a node

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 7.5, 8.0
• Component/s: AutoScaling, SolrCloud
• Assignee: Shalin Shekhar Mangar
• Reporter: Shalin Shekhar Mangar
• Created: 14/Feb/18 23:23
• Updated: 02/Oct/19 17:25
• Resolved: 05/Sep/18 10:39

Description

It is necessary to co-locate replicas of different collection together in a node when cross-collection joins are performed.

while creating a collection specify the parameter withCollection=other-collection-name . This ensure that Solr always ensure that atleast one replica of other-collection is present with this collection replicas
This requires changing create collection, create shard and add replica APIs as well because we want a replica of collection A to be created first before a replica of collection B is created so that join queries etc are always possible.

Some caveats to this implementation:

1. The other-collection should only have a single shard named "shard1"
2. Any replica of other-collection created by this feature will be of NRT type

Removing the above caveats can be a goal of other issues.

Issue Links

• contains: SOLR-12681 When a collection creation fails b/c autoscaling policy rules cannot be satified it leaves the empty state behind
• incorporates: SOLR-12681 When a collection creation fails b/c autoscaling policy rules cannot be satified it leaves the empty state behind
• is related to: SOLR-12506 Add SolrJ support for the modify collection API
• is related to: SOLR-12507 Modify collection API should support un-setting properties
• relates to: SOLR-9735 Umbrella JIRA for Auto Scaling and Cluster Management in SolrCloud