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

mongod_returns_no_cluster_time_without_keys.js should wait for shard primary to load cluster time keys

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.1
    • Component/s: Sharding
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Linked BF Score:
      16

      Description

      mongod_returns_no_cluster_time_without_keys.js starts up a sharded cluster and asserts that if there are keys in admin.system.keys, then responses to clients without the advanceClusterTimePrivilege from a shard primary will include $clusterTime. This isn't actually guaranteed right away because only mongos blocks during startup waiting for signing keys, not shards, and it's possible the shard primary may not have refreshed and loaded the keys into its KeyManager cache, which leads to a response with no $clusterTime.

      This test should instead use an assert.soon() loop for the first request that expects $clusterTime from a shard since it should eventually load the keys and every response after that should be signed.

        Attachments

          Activity

            People

            Assignee:
            lamont.nelson Lamont Nelson
            Reporter:
            jack.mulrow Jack Mulrow
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: