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

dropping a collection with long index names via rename fails under MMAPv1

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Critical - P2 Critical - P2
    • 3.6.8, 4.0.3, 4.1.3
    • Affects Version/s: 3.6.7, 4.0.2
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • Storage NYC 2018-09-10, Storage NYC 2018-09-24

      In a replica set running with the storage engine MMAPv1, a collection rename with the dropTarget option set to true may fail when the destination namespace refers to a collection with long index names approaching the MMAP namespace limit of 127 characters.

      The renameCollection operation would return an error with the code 10080 and a message containing the target namespace (the collection being replaced):

          "errmsg" : "ns name test.system.drop.1536175136i10t1.t.$aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa (size: 155) too long, max size is 127 bytes",
          "code" : 10080,

            benety.goh@mongodb.com Benety Goh
            benety.goh@mongodb.com Benety Goh
            0 Vote for this issue
            7 Start watching this issue