[SERVER-68042] Registration of duplicate range deletion task must return original completion future Created: 14/Jul/22 Updated: 29/Oct/23 Resolved: 26/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-08-08 |
| Participants: |
| Description |
|
Currently, trying to register twice a task on the range deleter service results in an error. Purpose of this ticket is to change the behavior to simply return the completion future of the already scheduled task. It will also be needed to adapt this unit test. |
| Comments |
| Comment by Githook User [ 26/Jul/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |