[SERVER-68774] Simplify `RangeDeleterService::registerTask` by removing `blockUntilRegistered` Created: 12/Aug/22 Updated: 29/Oct/23 Resolved: 29/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-2849-optimizations | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
Currently, RangeDeleterService::registerTask is using the blockUntilRegistered promise to "block" the future chain and invalidate it when trying to schedule a duplicated task. Purpose of this ticket is to remove the blockUntilRegistered promise and replace the insert in the set with the following:
|
| Comments |
| Comment by Githook User [ 29/Sep/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |