Config metadata commands should not use readConcern majority

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.0-rc0
    • Affects Version/s: 3.7.1
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2018-04-09, Sharding 2018-04-23, Sharding 2018-05-07, Sharding 2018-05-21
    • 20
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Blake Oler
              Reporter:
              Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: