[SOLR-13247] Incorrect shard placement during Collection creation

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 7.6, 7.7
• Component/s: SolrCloud
• Assignee: Unassigned
• Reporter: Bram VD
• Created: 14/Feb/19 10:18
• Updated: 08/Jun/19 15:02

Description

TL;DR; createNodeSet & shards combination is not being respected.

I'm attempting to create a collection with multiple shards, but
apparently the value of createNodeSet is not being respected and shards
are being assigned to nodes seemingly at random.

createNodeSet.shuffle is set to false, so that's not the cause.
Furthermore, sometimes not all nodes in the request are used.

Here's the create request, cleaned up for legibility. Note that the node names
are IP addresses but I've removed the first 3 octets for legibility.

admin/collections
?action=CREATE
&name=collectionName
&router.name=implicit
&shards=collectionName1,collectionName2,collectionName3,collectionName4,collectionName5,collectionName6
&maxShardsPerNode=1024
&collection.configName=some_config
&createNodeSet=171:8180_solr,172:8180_solr,173:8180_solr,177:8180_solr,179:8180_solr,179:8180_solr
&createNodeSet.shuffle=false
&waitForFinalState=true

Note that I'm creating a collection with 6 shards across 5 nodes.

Requested:
collectionName1: 171:8180_solr
collectionName2: 172:8180_solr
collectionName3: 173:8180_solr
collectionName4: 177:8180_solr
collectionName5: 179:8180_solr
collectionName6: 179:8180_solr

Actual:
collectionName1: 177:8180_solr
collectionName2: 172:8180_solr
collectionName3: 179:8180_solr
collectionName4: 173:8180_solr
collectionName5: 171:8180_solr
collectionName6: 171:8180_solr

Not a single shard ends up on the requested node.

Issue Links

• is part of: SOLR-13248 Autoscaling based replica placement is broken out of the box
• relates to: SOLR-12944 Bugs around createNodeSet=EMPTY