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

Initial sync bootstrap needs to handle collection metadata changes idempotently

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
    • Fully Compatible
    • ALL
    • Repl 2016-09-19, Repl 2016-10-10, Repl 2016-11-21
    • 0

      During an initial sync, due to the way the collection catalogs are gleaned from the sync source, it is difficult to always accurately reflect the collection catalog at the time a given op was generated on the primary, at op application time.
      Therefore, we must take extra steps to handle possible errors generated from certain ops that depend on accurate collection metadata. Some examples include collMod, createIndex, dropIndex, and createCollection.
      For certain errors, we must ignore the error and subsequently ensure that another specific metadata operation is seen in the oplog stream before reaching minValid.

            Assignee:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: