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

Tenant oplog applier doesn't commit the no-op writes which can make tenant migration to hang.

    • Fully Compatible
    • ALL
    • Repl 2020-12-14
    • 22

      Currently, tenant oplog applier doesn't commit the no-op writes, but still forwarding the _lastAppliedOpTimesUpToLastBatch's recipient opTime. This can make the donor opTime waiters (recipientSyncData cmd) to hang indefinitely waiting on a recipient opTime that doesn't correspond to any oplog entry to be majority replicated.
      + Change streams are also affected as it won't be able to see the progress.

            Assignee:
            suganthi.mani@mongodb.com Suganthi Mani
            Reporter:
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: