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

Migration of txn oplog entries can trigger fassert in secondary replication

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.6.0-rc6
    • Fix Version/s: 3.6.1, 3.7.1
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.6
    • Sprint:
      Sharding 2018-01-01

      Description

      During migration, oplog entries generated by transactions are converted to type 'n' no-op entries and sent to the destination side. These new oplog entries also retain the original fields, like 'ns' and 'uuid'. If the collection with the same name is drop and re-sharded, the secondaries will trigger an fassert when processing this type 'n' entries because the uuid no longer exists.

      Example log in secondary:

      Fatal assertion 16359 NamespaceNotFound: Failed to apply operation due to missing collection (32c50ae4-cec3-4f80-b70a-d1a60a74835c): ...
      

        Attachments

          Activity

            People

            Assignee:
            renctan Randolph Tan
            Reporter:
            renctan Randolph Tan
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: