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

fix collMod to update by UUID during oplog application

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
    • ALL
    • v3.6
    • Storage NYC 2018-05-21
    • 65

      These can happen due to initial sync idempotency requirements. Consider:
      Node 1: create A with uuid 1
      Node 2: start fetching oplog from Node 1
      Node 1: collMod A with uuid 1
      Node 1: rename A with uuid 1 to B
      Node 1: create A with uuid 2
      Node 2: clone collection A with uuid 2
      Node 2: try to apply collMod on A with uuid 1

            Assignee:
            xiangyu.yao@mongodb.com Xiangyu Yao (Inactive)
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: