[SERVER-66349] Recipient monitors are not shut down when internal error aborts split operation Created: 10/May/22 Updated: 29/Oct/23 Resolved: 12/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Didier Nadeau | Assignee: | Didier Nadeau |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Server Serverless 2022-05-16 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 146 | ||||||||
| Description |
|
The recipient server monitors are shutdown when either the recipient nodes report the recipient setName, or the abortToken is cancelled. However, the abortToken is only ever cancelled when a user explicitly calls abortShardSplit, an internal error causes us to abort the operation does not cancel the token. This means an internal error may leave the split acceptance future in a hung state, and never properly clean up the monitors. |
| Comments |
| Comment by Githook User [ 12/May/22 ] |
|
Author: {'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}Message: |