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

Possibility to get a non-existent key if using ReadConcern level:local when reading signing keys in ReplicaSet

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.6.12, 4.0.8
    • 4.0.11, 4.2.0-rc3, 4.3.1
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.2, v4.0, v3.6
    • Sharding 2019-05-06, Repl 2019-06-03, Sharding 2019-06-17, Sharding 2019-07-01

    Description

      There is a possible scenario that admin.system.keys collection gets diverged and hence customer gets a signing key that does not exists which causes errors in query processing.
      The proposed fix is to use ReadConcern level:majority when reading keys

      Attachments

        1. server-40535.diff
          6 kB
        2. test.js
          1 kB

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. SERVER-52955 KeysCollectionClientDirect should check if majority read concern is supported by storage engine

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

          Activity

            People

              misha.tyulenev@mongodb.com Misha Tyulenev
              misha.tyulenev@mongodb.com Misha Tyulenev
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: