Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2018-11-05, Sharding 2020-04-20, Sharding 2020-05-04, Sharding 2020-05-18
Linked BF Score:
0
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

Currently, the coordinator waits for all participants to ack the decision before returning the decision to the client.

Once a participant with a prepared transaction blocks requests with a higher transaction number rather than return PreparedTransactionInProgress (~~SERVER-38028~~), the coordinator can return to the client as soon as the commit decision is persisted (with the user's requested writeConcern, including journaling preference).

Note that if the user requested w:1 writeConcern, the decision may roll back after being reported to the client, but regardless all participants will apply the same decision.

depends on

SERVER-36640 Add way for TransactionCoordinator to signal when the commit decision is made and persisted

Closed

SERVER-38028 Participant with prepared transaction on session should block request for higher txn number on session rather than failing the new request

Closed

duplicates

SERVER-37882 Switch the distributed transaction commit protocol to the RPC protocol

Closed

is related to

SERVER-47993 Make coordinateCommitTransaction return the decision once the decision has been written with the user's writeConcern

Closed

related to

SERVER-47890 Unblacklist report_post_batch_resume_token.js from change_streams_sharded_collections_passthrough suites

Closed

SERVER-49423 Do not set coordinateCommitReturnImmediatelyAfterPersistingDecision in change stream multiversion suites

Closed

SERVER-52988 Unblacklist remaining test cases in txn_commit_optimizations_for_read_only_shards.js

Closed

SERVER-63971 Change server parameter to default to read-your-writes behavior after 2PC transaction

Closed

SERVER-64515 Remove claims of prepare behavior from linearizable reads

Open

SERVER-47130 Reduce w:majority commits from 4 to 2 in 2 PC

Backlog

(5 related to)

Assignee:: Cheahuychou Mao
Reporter:: Matthew Saltz (Inactive)
Participants:: Cheahuychou Mao, Esha Maharishi, Githook User, Matthew Saltz, Mira Carey, Tess Avitabile
Votes:: 0 Vote for this issue
Watchers:: 14 Start watching this issue

Created:: Sep 27 2018 08:45:20 PM UTC
Updated:: Oct 29 2023 10:27:50 PM UTC
Resolved:: May 06 2020 08:14:54 PM UTC
Confidence Status Last Update:: 24/Apr/20 4:57 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates