[SERVER-32230] shardCollection hangs with very long collection name Created: 08/Dec/17  Updated: 27/Oct/23  Resolved: 26/Mar/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Blake Oler
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Steps To Reproduce:

Connect to mongos via shell and run the following commands:

var collName = 'runCommand( {geoSearch:<collection>, search:{a:1}, near:[-33.3,89.9], maxDistance:314159265007} )';
db.adminCommand({ enableSharding: 'test' });
db.adminCommand({ shardCollection: 'test.' + collName, key: {a: 'hashed'} });

Sprint: Sharding 2018-04-09
Participants:
Linked BF Score: 0

 Description   

Shard errors with "User Assertion: 73:fully qualified namespace ... is too long ...", but config keeps on retrying anyways.



 Comments   
Comment by Blake Oler [ 26/Mar/18 ]

Behavior observed on the diff that the BF is linked to. On master, the issue no longer exists. Closing as gone away.

Generated at Thu Feb 08 04:29:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.