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

Add JS/client function to retry moveChunk on mongod stepdown related errors

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None

      Description

      If a moveChunk operation fails because one of the mongods involved in the migration (donor or recipient) stepped down, the client should retry the moveChunk operation.

      *NOTE*
      SERVER-22822 should be reverted whenever the retry moveChunk helper works. The changes prevented mongod step downs rather than retrying the moveChunk operation, and will no longer be necessary when there's a retry.

        Attachments

          Issue Links

          depends on

          Task - A task that needs to be done. SERVER-24856 Manual moveChunk requests should go through the balancer running on the CSRS primary

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-24866 Balancer should be able to recover its state after CSRS primary stepdown/crash

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-22822 Prevent mongod step down during moveChunk in balance_repl.js and sharding_rs2.js

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              dianna.hohensee Dianna Hohensee
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: