fix collMod to update by UUID during oplog application

XMLWordPrintableJSON

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

      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 (Inactive)
            Reporter:
            Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: