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

Make the migration chunk cloner source resilient to stepdowns and network errors

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding
    • 20

    Description

      On the donor shard, the MigrationChunkClonerSourceLegacy::startClone code uses _callRecipient private class function to call the recipient, which then uses the task executor to make the call. The task executor does not retry NotMaster errors.

      A solution would be to use a ShardRemote, instead, and allow NotMaster errors to be retried for that first command, _recvChunkStart – don't want to use it for all commands, but the first one is safe, I think.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: