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

Introduce means to disable sharding minOpTime recovery

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.2.0-rc1
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding B (10/30/15)

    Description

      With the introduction of Config Servers as Replica Sets, shard hosts will checkpoint the latest config server opTime after each metadata operation they perform and if necessary on startup will contact the config server's primary in order to recover the minOpTime that they should be using.

      This poses problems with restoring a host, which was previously backed up with this recovery information, because it will attempt to connect a potentially defunct config server.

      For this reason, we need to either have a separate argument, which allows the recovery information to be ignored or we should start requiring --shardSvr to be specified for all shard servers.

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. SERVER-20943 Write procedures for restoring a CSRS sharded cluster

          • Major - P3 - Major loss of function.
          • Closed
          is documented by

          Task - A task that needs to be done. DOCS-6435 Document how to disable sharding state recovery (and what that means)

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-19934 Ill-timed crash at end of chunk migration can lead to lost writes when using replica sets as config servers

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

          Task - A task that needs to be done. DOCS-6435 Document how to disable sharding state recovery (and what that means)

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-20824 Test for sharding state recovery

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

          Activity

            People

              spencer@mongodb.com Spencer Brody (Inactive)
              kaloian.manassiev@mongodb.com Kaloian Manassiev
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: