[DRIVERS-1325] Investigate changes in PM-1724: Make Validate more resilient Created: 09/Jul/20 Updated: 22/Sep/21 Resolved: 28/Jul/20 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Downstream Change Summary This project will enable Atlas validation checking to be much more reliable, and could allow us to start running validate on live Atlas nodes instead of spawning temporary copies for that purpose. Description of Linked TicketEpic Summary SummaryThis project is to improve the validate command to address the failures we identified when running validate in Atlas. There were a small number of replica sets that validation can never complete. MotivationAtlas wants to run validate command continuously. Thus it has to behave predictably. In case of failure of validate command, it should be easy to understand the reason and come up with the actions to be taken before retrying. Cast of Characters
Documentation |
| Comments |
| Comment by Alexander Golin (Inactive) [ 13/Jul/20 ] |
|
Should not need any changes from Drivers |