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

Add a server comment in tenant oplog applier for shard merge oplog application mode & isDataConsistent true value.

    • Serverless
    • Fully Compatible
    • ALL
    • Server Serverless 2023-03-20

      When a recipient failover happens in the middle of tenant oplog application, we might resume applying those donor oplog entries from a point that was already applied due to the fact we first apply the donor oplog entries and then write no-op donor oplog entries for the given batch and we calculate the resume point by finding the latest no-op oplog entry . So, with the stricter mode 'kSecondary', re-applying those donor oplog entries can cause failure and leads to shard merge failure unnecessarily. So, change the tenant oplog application mode to kInitialSync (lenient mode)

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

              Created:
              Updated:
              Resolved: