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

Investigate fetching metadata from the CSRS using hedged reads

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • 200

      In a CSRS, and particularly in a config shard, it is common to experience lagged replica set nodes.

      If the lagged node is the nearest to a request, a refresh can time out while waiting to satisfy the afterClusterTime.

      The goal of this ticket is to make a proposal to exclusively use hedged reads when fetching metadata from CSRS for installing filtering or routing information, in order to be resilient to nearest lagged secondaries.

            Assignee:
            Unassigned Unassigned
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: