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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.6.12, 4.0.8
    • Fix Version/s: 4.0.11, 4.2.0-rc3, 4.3.1
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2, v4.0, v3.6
    • Sprint:
      Sharding 2019-05-06, Repl 2019-06-03, Sharding 2019-06-17, Sharding 2019-07-01
    • Case:

      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

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: