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

Make sure the shard merge never leaves an orphaned open backup cursor on donor.

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Serverless

    Description

      Currently, we ignore errors that's returned for kill backup cursor command. So, shard merge can miss killing the backup cursor opened on the donor primary due to recipient primary shutdown or due to some transient n/w error. This would be bad, especially, when there is an orphaned active backup cursor on donor on shard merge abort. Currently, we only allow one active open backup cursor on a node at any point of time. This would shard merge retry or backup service to cause outage.

      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: