[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:
Problem/Incident
causes SERVER-65905 Shard split test times out non determ... Closed
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: SERVER-66349 Cancel abortSource when aborting a shard split due to an error
Branch: master
https://github.com/mongodb/mongo/commit/1f47628874cb9341b89b12be167dd81c5ed508ae

Generated at Thu Feb 08 06:05:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.