[DRIVERS-2622] Add SDAM tests for standalone restarted as a replica set or mongos Created: 03/May/23 Updated: 19/Sep/23 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | SDAM |
| Fix Version/s: | None |
| Type: | Task | Priority: | Unknown |
| Reporter: | Shane Harvey | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Driver Changes: | Needed | ||||||||
| Description |
SummaryAdd SDAM tests to ensure the TopologyType remains "Single" when a standalone node is restarted as a replica set or mongos. The SDAM spec says:
PyMongo supports online change from standalone to replica set and standalone to sharded. The tests added in this change would confirm that behavior in all drivers. MotivationWho is the affected end user?Who are the stakeholders? How does this affect the end user?Are they blocked? Are they annoyed? Are they confused? How likely is it that this problem or use case will occur?Main path? Edge case? If the problem does occur, what are the consequences and how severe are they?Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete? Is this issue urgent?Does this ticket have a required timeline? What is it? Is this ticket required by a downstream team?Needed by e.g. Atlas, Shell, Compass? Is this ticket only for tests?Does this ticket have any functional impact, or is it just test improvements? Acceptance CriteriaWhat specific requirements must be met to consider the design phase complete? |