[SERVER-71383] ReshardingCoordinatorService doesn't fulfill promises on executor shutdown Created: 15/Nov/22 Updated: 29/Oct/23 Resolved: 16/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc2, 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Abdul Qadeer | Assignee: | Abdul Qadeer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v6.2
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 135 | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
In BF-26723, it was found that the ReshardingCoordinatorService relies on the executor to emplace promises after running _isReshardingOpRedundant(). If the executor is shut down as part of stepDown(), the `onCompletion` in chain is not run that causes unfulfilled promises resulting in invariant failure when the old primary instances are destroyed. One fix is to run the cleanup on a different executor. |
| Comments |
| Comment by Githook User [ 16/Nov/22 ] |
|
Author: {'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}Message: (cherry picked from commit 92b2f2d4bf503dfe9a9bf2cc02770f7a66b8c2a1) |
| Comment by Githook User [ 16/Nov/22 ] |
|
Author: {'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}Message: |