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

Implement awaitable isMaster client protocol without exhaustAllowed

    • Type: Icon: Improvement Improvement
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Internal Client
    • Labels:
      None
    • Service Arch 2020-01-27, Service Arch 2020-02-10, Service Arch 2020-02-24

      Awaitable isMaster can be triggered via the use of topologyVersion and maxAwaitTimeMS fields. We should begin to use these isMasters with the ReplicaSetMonitor scanning. This does not require use of exhaust/tailable cursors.

      The use of awaitable isMaster may need to be opt-in for testing until we have mongodden/mongossen that support this work. However, this work should be verified for correctness via modification of existing integration tests and js test suites.

            Assignee:
            janna.golden@mongodb.com Janna Golden
            Reporter:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: