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

XMLWordPrintableJSON

    • Cluster Scalability
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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)

            Assignee:
            [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            Misha Tyulenev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: