[SERVER-55396] Drop database coordinator retries indefinetly until stepdowns Created: 22/Mar/21 Updated: 03/May/21 Resolved: 20/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | Backlog |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | PM-1965-Milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently the drop database coordinator is only partially resilient to CSRS/participant stepdowns or network partitions, in fact currently we rely on the retry logic of some other component such as the runCommandWithFixedRetryAttempts function that is retrying just 3 times. The goal of this ticket is to make the drop database coordinator retries all its phases indefinitely until a stepdown happen. |
| Comments |
| Comment by Marcos José Grillo Ramirez [ 20/Apr/21 ] |
|
The work for this ticket will be generalized and implemented by SERVER-55150 |