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

Handle collectionUUID in config.chunks on upgrade/downgrade

    • Fully Compatible

      Patch up config.chunks entries in the following ways:

      • Remove the collectionUUID field during downgrade
      • Add the collectionUUID field during upgrade

      Current config server config.chunks collection format (before upgrade / after downgrade):

      {
            _id : "test.foo-a_MinKey",
            ns : "test.foo",
            min : {
                    "a" : { "$minKey" : 1 }
            },
            max : {
                    "a" : { "$maxKey" : 1 }
            },
            shard : "test-rs1",
            lastmod : Timestamp(1, 0),
            lastmodEpoch : ObjectId("587fc60cef168288439ad6ed"),
            jumbo : false              // optional field
         }
      

      New config server config.chunks collection format (before downgrade / after upgrade):

      {
            _id : "test.foo-a_MinKey",
            uuid : "9ecb0808-b62b-4204-9f99-8c65c9e6e10b",
            min : {
                    "a" : { "$minKey" : 1 }
            },
            max : {
                    "a" : { "$maxKey" : 1 }
            },
            shard : "test-rs1",
            lastmod : Timestamp(1, 0),
            lastmodEpoch : ObjectId("587fc60cef168288439ad6ed"),
            jumbo : false              // optional field
         }
      

            Assignee:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: