[SERVER-44826] Change config.rangeDeletions optional 'pending' flag to required 'readyToDelete' Created: 25/Nov/19 Updated: 06/Dec/22 Resolved: 18/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Sprint: | Sharding 2019-12-16 |
| Participants: |
| Description |
|
Originally we designed the config.rangeDeletions collection to have a 'pending' boolean flag whose presence indicated that the range was not yet ready to delete, and doing an $unset operation on that flag would trigger range deletions. After spending a little time with that implementation it seems like it would make more sense to just have a non-optional flag 'readyToDelete' which is either true or false, and setting the value to true is what triggers deletion. We will do this ticket in a final pass after other functionality is in, since this is really just cleanup work. |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 18/Feb/20 ] |
|
Closing because it is not important for correctness. |