Changes made by applyOps during migration may not be propagated to the destination shard

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.8.0-rc2
    • Component/s: Sharding
    • None
    • Sharding
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      MigrateFromStatus::logOp currently ignores all commands so any document updates during a migration with applyOps can be missed if the document was cloned before the applyOps.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: