Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Won't Fix
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
- prepare_optional

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

A "prepare" field is added temporarily on applyOps command in ~~SERVER-35307~~ to avoid passing the same field on oplog entry down to command execution code path on secondaries. Once ~~SERVER-35880~~ is done, the prepared "applyOps" will not be applied as a command, then we will remove this duplicate field.

depends on

SERVER-35880 Apply ops within a prepare oplog entry in parallel, and mix them in with other CRUD ops

Closed

related to

SERVER-35307 Serially within their own batch, secondaries should put prepared transactions in a prepared state and immediately abort them.

Closed

SERVER-39809 Remove the "prepare" root field of oplog entry

Closed

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Siyuan Zhou
Participants:: [DO NOT USE] Backlog - Replication Team, Matthew Russotto, Siyuan Zhou
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Aug 22 2018 10:56:30 PM UTC
Updated:: Dec 06 2022 03:19:57 AM UTC
Resolved:: May 12 2019 10:53:57 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates