[SERVER-32338] Update secondary oplog application machinery to know how to correctly parallelize application of transaction oplog entries Created: 14/Dec/17  Updated: 06/Dec/22  Resolved: 17/May/19

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

Type: Task Priority: Major - P3
Reporter: Gregory McKeon (Inactive) Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: bigtxns_optional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-32337 Change the inner oplog entries within... Closed
Duplicate
duplicates SERVER-39434 Apply the new "commit" oplog entry fo... Closed
Related
related to SERVER-32913 Parallelize application of applyOps o... Closed
Assigned Teams:
Replication
Participants:

 Comments   
Comment by Siyuan Zhou [ 25/Mar/19 ]

We only parallelize unprepared transactions on secondary as part of SERVER-39434. This ticket is to parallelize prepared transactions application.

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