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

Explore using RSM monitor pings to update the topologyTime for ShardRegistry

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 1

      Currently, the ShardRegistry has a thread periodically sending pings to the CSRS primary to fetch the latest topology time (SERVER-91121).

      The ShardRegistry instantiates a ReplicaSetMonitor for the config server. The RSM periodically pings the nodes of the set, so we might be able to use these pings to gossip the topology time from the CSRS, and remove the periodic update thread.

            Assignee:
            Unassigned Unassigned
            Reporter:
            yujin.kang@mongodb.com Yujin Kang Park
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: