-
Type: Task
-
Resolution: Works as Designed
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:None
Description
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.)
- documents
-
SERVER-47363 Define correct use of MemberIds in Atlas workflow tests
- Closed