[SERVER-39510] Test that transaction coordinator going down does not lead to catastrophic failure Created: 11/Feb/19  Updated: 29/Oct/23  Resolved: 13/May/19

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: None
Fix Version/s: 4.1.12

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-39036 Stop pinning stable timestamp behind ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-04-08, Repl 2019-04-22, Repl 2019-05-06, Repl 2019-05-20
Participants:

 Description   

Test that if the transaction coordinator shard goes down completely while a transaction is prepared on participants, the stable timestamp is still able to advance on the participants, both on the primary and on secondaries.



 Comments   
Comment by Githook User [ 09/May/19 ]

Author:

{'name': 'Pavi Vetriselvan', 'username': 'pvselvan', 'email': 'pvselvan@umich.edu'}

Message: SERVER-39510 test that txn participant can make progress even if txn coordinator goes down
Branch: master
https://github.com/mongodb/mongo/commit/1d2038b2b84172abbe06ead3a2fa80f833998651

Generated at Thu Feb 08 04:52:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.