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

Config metadata commands should not use readConcern majority

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.7.1
    • 4.0.0-rc0
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2018-04-09, Sharding 2018-04-23, Sharding 2018-05-07, Sharding 2018-05-21
    • 20

    Description

      For example, in removeShard command it get trigger a ShardRegistry refresh, but it uses the same operation context to do a readConcern majority read, and this can cause some weird behavior because the command will think that shards exists, when in fact they no longer do.

      Attachments

        Issue Links

          Activity

            People

              blake.oler@mongodb.com Blake Oler
              randolph@mongodb.com Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: