Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
None

Assigned Teams:

Replication
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

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.

duplicates

SERVER-38165 Test that prepared transactions work with an in-memory secondary

Closed

is related to

SERVER-35786 lastDurable optime should be updated after batch application on non-durable storage engines

Backlog

SERVER-36782 WT erring because commit timestamp is older than stable timestamp

Closed

related to

SERVER-36023 Try to enable replica set transaction testing with the inMemory WT storage engine

Closed

SERVER-38165 Test that prepared transactions work with an in-memory secondary

Closed

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Dianna Hohensee (Inactive)
Participants:: [DO NOT USE] Backlog - Replication Team, Dianna Hohensee, Judah Schvimer
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Nov 06 2018 05:04:24 PM UTC
Updated:: Dec 06 2022 03:13:49 AM UTC
Resolved:: Apr 22 2019 06:13:46 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates