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

Ensure shard Merge recipient aborts correctly on rollbacks and restarts.

    • Fully Compatible
    • v7.1
    • Server Serverless 2023-03-20, Server Serverless 2023-04-03, Server Serverless 2023-04-17, Server Serverless 2023-05-01, Server Serverless 2023-05-15, Server Serverless 2023-05-29, Server Serverless 2023-07-24, Server Serverless 2023-08-07, Server Serverless 2023-08-21, Server Serverless 2023-09-04

      Shard Merge is not robust to donor/recipient failovers, restarts and rollbacks. So, the following items should be taken care by this ticket
      1) ShardMergeRecipientService is interrupted correctly during rollback/shutdown/abort migration cases.
      2) Any data (includes temp WT directory, imported collection, idents to mdb catalog and storage) /resources (eg. backup cursor) that are copied/allocated as part of failed migration attempt is deleted/freed correctly upon node rollback/restart and abort migration cases.
      3) No data corruption due to restarts/rollbacks after migration is committed.

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

              Created:
              Updated:
              Resolved: