Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2019-03-11, Sharding 2019-04-22
Linked BF Score:
11
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, in order to test coordinator failover, we have an override that causes the router to always use the config server as the coordinator shard for a transaction. Once prepare failover is ready, we should move the coordinator back onto the first shard to be touched by a transaction.

depends on

SERVER-35872 Reconstruct prepared transactions on replication rollback

Closed

SERVER-39036 Stop pinning stable timestamp behind prepared transactions

Closed

SERVER-40081 Move session checkout to before command execution

Closed

is depended on by

SERVER-40220 Remove "config server is coordinator" failpoint from mongos and "doNotForgetCoordinator" failpoint from mongod

Closed

Assignee:: Jack Mulrow
Reporter:: Matthew Saltz (Inactive)
Participants:: Esha Maharishi, Githook User, Jack Mulrow, Matthew Saltz
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Nov 01 2018 10:24:33 PM UTC
Updated:: Oct 29 2023 10:26:56 PM UTC
Resolved:: Apr 17 2019 08:48:40 PM UTC
Confidence Status Last Update:: 10/Apr/19 9:59 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates