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

Handle recipient secondary failures while performing file copy based cloning procedure.

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Serverless

    Description

      Currently I am not clear on how we handle errors on recipient secondaries while copying & importing donor files. 

      1) Say copying a particular donor file failed on recipient secondary, how do we prevent recipient secondaries from copying subsequent donor files? The current design is that for each entry in the backup cursor response (donor files to be imported list), we generate an oplog entry and an op observer for that entry would trigger the copying of that particular file. 

      2) Does recipient secondary need to inform recipient primary to abort merge?

      Attachments

        Activity

          People

            backlog-server-serverless [DO NOT USE] Backlog - Server Serverless (Inactive)
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: