Explore using RSM monitor pings to update the topologyTime for ShardRegistry

XMLWordPrintableJSON

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

      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
              Reporter:
              Yujin Kang Park
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: