Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Won't Fix
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
- prepare_optional
- prepare_upgrade_downgrade

Assigned Teams:

Replication

We must not allow transactions on shard servers when the featureCompatibilityVersion is 4.0.

When a replica set is part of a sharded cluster, we can issue transaction commands through multiple routers. This allows us to target primaries in decreasing term order, which can lead to an anomaly where a transaction can go from aborted to committed. This is addressed in FCV 4.2 by performing a write when a transaction is aborted (~~SERVER-38132~~) and aborting a transaction when we return NoSuchTransaction (~~SERVER-38133~~).

is related to

SERVER-38850 Perform noop write before returning NoSuchTransaction error

Closed

related to

SERVER-38132 Aborting a transaction must always update config.transactions and write an abort oplog entry

Closed

SERVER-38133 When asked to continue a transaction whose txnNumber is too new, TransactionParticipant must abort that transaction

Closed

SERVER-38134 Ensure config.transactions and TransactionParticipant have consistent state after every command

Closed

Assignee:: [DO NOT USE] Backlog - Replication Team

Reporter:: Tess Avitabile (Inactive)

Participants:: [DO NOT USE] Backlog - Replication Team, Judah Schvimer, Tess Avitabile

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: Nov 14 2018 08:59:42 PM UTC

Updated:: Dec 06 2022 03:12:38 AM UTC

Resolved:: May 17 2019 06:49:09 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates