Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.3.0-rc4
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2022-02-07, Sharding 2022-02-21, Sharding 2022-03-07, Sharding NYC 2022-03-21
Linked BF Score:
150
Story Points:
3
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

Make resharding recipients log and apply oplog entries for retryable internal transactions just like it does for oplog entries for retryable writes
Verify that retryability works correctly for cross-shard transactions.

depends on

SERVER-58756 [Retryability] Add retryability support for internal transactions for retryable writes

Closed

split to

SERVER-63441 [Retryability] Handle retryable internal transactions with multiple oplog entries when migrating sessions during resharding

Closed

SERVER-63444 [Retryability] Make retryable findAndModify executed in internal transactions retryable across resharding

Closed

SERVER-63877 Determine if resharding should migrate internal sessions for non-retryable writes

Closed

SERVER-63880 [Retryability] Make resharding handle applyOps oplog entries with WouldChangeOwningShard sentinel noop entry

Closed

Assignee:: Cheahuychou Mao
Reporter:: Cheahuychou Mao
Participants:: Cheahuychou Mao, Githook User, Jack Mulrow, Lamont Nelson
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Oct 07 2021 03:09:01 PM UTC
Updated:: Oct 29 2023 09:47:41 PM UTC
Resolved:: Mar 09 2022 09:48:44 PM UTC
Confidence Status Last Update:: 31/Jan/22 9:05 PM