Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
Server Serverless 2022-05-16
-
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.
Attachments
Issue Links
- causes
-
SERVER-65905 Shard split test times out non deterministically
-
- Closed
-