Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2019-02-25, Repl 2019-03-11
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

Pass the commit oplog entry timestamp as the durable_timestamp when committing a prepared storage transaction.

depends on

SERVER-39064 Storage interface changes for specifying durable_timestamp

Closed

WT-4505 Add ability to manage when prepared transactions appear in checkpoints

Closed

is depended on by

SERVER-39036 Stop pinning stable timestamp behind prepared transactions

Closed

SERVER-39042 Choose commit timestamp for transaction as max(prepare timestamps)

Closed

is related to

SERVER-39782 Replaying prepared transaction writes for commit oplog entry during replication recovery and initial sync should set commit and durable timestamp for those writes.

Closed

Assignee:: Suganthi Mani
Reporter:: Tess Avitabile (Inactive)
Participants:: Githook User, Suganthi Mani, Tess Avitabile, Vamsi Boyapati
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Jan 16 2019 02:47:07 PM UTC
Updated:: Oct 29 2023 10:25:04 PM UTC
Resolved:: Feb 26 2019 03:06:48 PM UTC
Confidence Status Last Update:: 11/Feb/19 2:36 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates