[DOCS-13745] Investigate changes in SERVER-47363: Define correct use of MemberIds in Atlas workflow tests Created: 03/Jul/20 Updated: 13/Nov/23 Due: 30/Apr/21 Resolved: 11/May/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Andrew Feierabend (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 3 years, 31 weeks, 6 days ago | ||||||||
| Epic Link: | DOCSP-9747 | ||||||||
| Story Points: | 2 | ||||||||
| Description |
DescriptionDownstream Change Summary Our recommendation to atlas is not to recycle member Ids while adding/replacing nodes to the replica set, to avoid problems like 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 TicketMemberIds 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 changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |