Uploaded image for project: 'Motor'
  1. Motor
  2. MOTOR-1018

SDAM should prioritize electionId over setVersion only on >=6.0 servers

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: SDAM
    • None
    • Hide

      DRIVERS-2412:

      • Sync spec changes in 37c32c
      • Confirm tests fail with current updateRSFromPrimary implementation
      • Summary of updateRSFromPrimary changes:
        • If maxWireVersion 17 or greater
        • Prioritize electionId before setVersion
        • Handle nullish values for both setVersion and electionId
        • always set maxElectionId and maxSetVersion together (they are a tuple value)
      • Confirm tests pass with changes

      Join #drivers-2412-sdam-should-prioritize-electionid-over-setversion on slack for any questions

      Show
      DRIVERS-2412 : Sync spec changes in 37c32c Confirm tests fail with current updateRSFromPrimary implementation Summary of updateRSFromPrimary changes: If maxWireVersion 17 or greater Prioritize electionId before setVersion Handle nullish values for both setVersion and electionId always set maxElectionId and maxSetVersion together (they are a tuple value) Confirm tests pass with changes Join #drivers-2412-sdam-should-prioritize-electionid-over-setversion on slack for any questions

      This ticket was split from DRIVERS-2412, please see that ticket for a detailed description.

            Assignee:
            Unassigned Unassigned
            Reporter:
            dbeng-pm-bot TPM Jira Automations Bot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: