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

Investigate changes in SERVER-47363: Define correct use of MemberIds in Atlas workflow tests

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: manual, Server
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      2
    • Sprint:
      ServerDocs2020: Apr27 - May4, ServerDocs2020: May4 - May11, ServerDocs2020: May11 - May18

      Description

      Description

      Downstream Change Summary

      Our recommendation to atlas is not to recycle member Ids while adding/replacing nodes to the replica set, to avoid problems like SERVER-47852. Also, to be noted, SERVER-48345 has increased the member id limit from 255 to INT_MAX.

      Atlas will update its workflow such that it aligns with the workflow mentioned in js test for adding new nodes to the replica set and for replacing nodes.

      Description of Linked Ticket

      MemberIds should uniquely identify nodes, even across config versions. Therefore reusing MemberIds can be dangerous. The current Atlas workflow tests will do whatever Atlas does today, but we should decide what the correct workflow is and change the tests to match that so Atlas can implement the correct workflow.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              andrew.feierabend Andrew Feierabend
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Andrew Feierabend Andrew Feierabend
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

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