Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-32230

shardCollection hangs with very long collection name

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.7.1
    • Component/s: Sharding
    • Labels:
      None
    • ALL
    • Hide

      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'} });
      
      Show
      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'} });
    • Sharding 2018-04-09
    • 0

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

            Assignee:
            blake.oler@mongodb.com Blake Oler
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: