Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2021-11-29, Sharding 2021-12-13, Sharding 2021-12-27, Sharding 2022-01-10, Sharding 2022-01-24
Story Points:
2
CAR Domain/s:
None

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

Make the OperationContext not set the txnRetryCounter for multi-document transactions to 0 by default. That is, if the client does not provide a txnRetryCounter, its value should be on the OperationContext boost::none.
Make TransactionParticipant and TransactionCoordinator have a way to track if the txnRetryCounter of multi-document transaction is client-specified or the default.

This is required by ~~SERVER-61088~~ where we only want to persist txnRetryCounter if the txnRetryCounter is initialized.

is depended on by

SERVER-61088 [Upgrade/downgrade] Make transaction participants check if txnRetryCounter is supported during startTransaction and have mongos use it

Closed

Assignee:: Jason Zhang (Inactive)
Reporter:: Cheahuychou Mao
Participants:: Cheahuychou Mao, Githook User, Jason Zhang
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Oct 28 2021 08:09:14 PM UTC
Updated:: Oct 29 2023 09:46:46 PM UTC
Resolved:: Jan 20 2022 03:00:59 PM UTC