Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.9.0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-234-M3
- PM-234-T-config-txn-clone

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2020-12-14
Story Points:
1
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

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

Assignee:: Max Hirschhorn
Reporter:: Max Hirschhorn
Participants:: Githook User, Max Hirschhorn
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Oct 12 2020 03:27:39 PM UTC
Updated:: Oct 29 2023 10:02:06 PM UTC
Resolved:: Dec 02 2020 12:39:38 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates