[SOLR-4983] Problematic core naming by collection create API

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: SolrCloud
• Assignee: Unassigned
• Reporter: Chris Toomey
• Created: 02/Jul/13 01:50
• Updated: 02/Jan/17 17:59

Description

The SolrCloud collection create API creates cores named "foo_shard<x>_replica<y>" when asked to create collection "foo".

This is problematic for at least 2 reasons:

1) these ugly core names show up in the core admin UI, and will vary depending on which node is being used,

2) it prevents collections from being used in SolrCloud joins, since join takes a core name as the fromIndex parameter and there's no single core name for the collection. As I've documented in https://issues.apache.org/jira/browse/SOLR-4905 and http://lucene.472066.n3.nabble.com/Joins-with-SolrCloud-tp4073199p4074038.html, SolrCloud join does work when the inner collection (fromIndex) is not sharded, assuming that collection is available and initialized at SolrCloud bootstrap time.

Could this be changed to instead use the collection name for the core name? Or at least add a core-name option to the API?

Issue Links

• relates to: SOLR-4905 Allow fromIndex parameter to JoinQParserPlugin to refer to a single-sharded collection that has a replica on all nodes