[SERVER-49052] Prohibit dropping the config db Created: 23/Jun/20 Updated: 12/Apr/21 Resolved: 17/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Connie Chen | Assignee: | Vishnu Kaushik |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | Execution Team 2020-07-13, Execution Team 2020-07-27, Execution Team 2020-08-10, Execution Team 2020-09-21 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 120 | ||||||||||||
| Description |
|
We would like to prohibit config from being dropped to prevent failures. This ticket is to investigate whether there’s some playbook that requires it in the field that cannot be modified. This originated from a failure where the fuzzier dropped the config database causing voteCommitIndexBuild to retry endlessly on NamespaceNotFound. Fixing the fuzzer only (to not drop config) wouldn't fix the problem that users can hang their index builds indefinitely since config.system.indexBuilds is missing. |
| Comments |
| Comment by Michael Gargiulo [ 17/Sep/20 ] |
|
Marking this as "Won't Do" - We have decided that to solve |