Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13381

Investigate changes in SERVER-44508: Add maxAwaitTimeMS and topologyVersion to isMaster command


      Downstream Change Summary

      The isMaster response includes topologyVersion: {processId: <objectID>, counter: <long>}. The processId is constant for the process's lifetime. The counter increments on significant topology changes such as stepdown, stepup, reconfig, featureCompatibilityVersion change, or anything else that changes the isMaster response.

      This isMaster command accepts two new fields topologyVersion (same type as above) and maxAwaitTimeMS. When these fields are supplied, the isMaster command waits up to maxAwaitTimeMS for the server's topologyVersion to exceed the client's requested topologyVersion. I'm not certain we should document these fields, since they are only expected to be used by mongos and drivers.

      Description of Linked Ticket

      Also return a dummy topologyVersion field in the isMaster reply.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

            kay.kim@mongodb.com Kay Kim (Inactive)
            backlog-server-pm Backlog - Core Eng Program Management Team
            0 Vote for this issue
            3 Start watching this issue

              4 years, 13 weeks ago