Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
Fully Compatible
-
Sharding 2020-12-14
-
1
Description
One option would be to schedule the callback on the Fetcher after the TransactionParticipant::onExitPrepare() future resolves. Another option would be to use a dedicated thread for the config.transactions cloner for resharding to prevent a liveness issue.
Attachments
Issue Links
- is depended on by
-
SERVER-52921 Integrate config.transactions cloner for resharding into RecipientStateMachine
-
- Closed
-
- related to
-
SERVER-53139 Don't wait for prepared transactions in resharding oplog applier writer thread
-
- Closed
-