Ignore NamespaceNotFound exceptions when applying transactions during initial sync and recovery

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.14
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2019-06-03
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The collection may have been dropped since we are applying operations out of order.

      We ignore NamespaceNotFound errors in normal oplog application here.

      But we don't do it here. The applyOps command doesn't seem to ignore these errors either, so wherever we use that code path to apply transaction operations we likely need to do the same.

      This was found from code inspection and I haven't created a repro, so it's possible something prevents this from causing a problem.

      It'll be interesting to see if the initial sync fuzzer catches this once it supports transactions, max.hirschhorn.

        1. initialSyncBug.js
          1.52 MB

            Assignee:
            Matthew Russotto
            Reporter:
            Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: