[SERVER-37943] Enable replica set transactions for the inMemory WT storage engine Created: 06/Nov/18  Updated: 06/Dec/22  Resolved: 22/Apr/19

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-38165 Test that prepared transactions work ... Closed
Related
related to SERVER-36023 Try to enable replica set transaction... Closed
related to SERVER-38165 Test that prepared transactions work ... Closed
is related to SERVER-35786 lastDurable optime should be updated ... Backlog
is related to SERVER-36782 WT erring because commit timestamp is... Closed
Assigned Teams:
Replication
Participants:

 Description   

This is a continuation of SERVER-36023, which attempted to turn on testing for replica set transactions after the Recoverable Rollback with In-Memory Storage Engine project. Testing could not be turned on, and further work is required. I have not explored the reasons for failure, but there is a clear deadlock when transactions are run on the inMemory storage engine. The solution might be simple, or it might not.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 22/Apr/19 ]

Closing this as a duplicate of SERVER-38165, because we enabled the requisite testing on that ticket.

Comment by Judah Schvimer [ 15/Nov/18 ]

We will investigate this after finishing cross-shard transactions, allowing the stable timestamp to advance beyond prepared transactions, and transactions larger than 16MB. In the meantime we will test in-memory secondaries in SERVER-38165.

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