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

Make ShardRegistry::_lookup() fail if topologyTIme apparently goes backwards

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding EMEA
    • Sharding EMEA 2023-02-06

      If the maxTopologyTime from the config.shards documents is lower than the cached topologyTime (cachedData.getTime().topologyTime), then the ShardRegistry is doomed to infinitely refresh until this is no longer true. Better would be for _lookup() to fail (ie. uassert) in this case, so that the underlying operation will fail in this unexpected situation.

            Assignee:
            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            Reporter:
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: