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

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

    XMLWordPrintable

    Details

      Description

      Description

      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.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 25 weeks, 4 days ago
                Date of 1st Reply: