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

KeysCollectionManager does not refresh immediately on 3.6 shard startup when added to a sharded claster

    XMLWordPrintable

    Details

    • Operating System:
      ALL
    • Linked BF Score:
      15

      Description

      The issue is observable only in v3.6 the BACKPORT-1861 made the absence of keys apparent as the clusterTime was removed from the metadata (before there was a dummy signature)

      The problem happens in an ReplicaSet started with shardsvr:true and later added to a sharded cluster or in a ShardingTest with auth

      The KeysCollectionManager starts the monitoring thread when the RS is aded to a cluster and does not make initial refresh but eventually refreshing within 30 seconds (default refresh interval)

        Attachments

          Activity

            People

            Assignee:
            backlog-server-sharding-nyc Backlog - Sharding NYC
            Reporter:
            misha.tyulenev Misha Tyulenev
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated: