[SERVER-37505] Run applyOps with prepare: true in its own batch in MultiApplier Created: 05/Oct/18  Updated: 29/Oct/23  Resolved: 08/Oct/18

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

Type: Bug Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Siyuan Zhou
Resolution: Fixed Votes: 0
Labels: prepare_durability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-35880 Apply ops within a prepare oplog entr... Closed
is related to SERVER-37506 Blacklist no_writes_to_config_transac... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2018-10-22
Participants:
Linked BF Score: 58

 Description   

Although steady state oplog application puts applyOps command with prepare: true in its own batch in SERVER-35307. The batcher of OplogApplier used by initial sync and replication recovery doesn't do that. SERVER-35880 will revert this and parallelizes oplog application of transaction operations. For initial sync and replication recovery, it's natural to parallelize transaction operations since we don't apply ops until we see the 'commitTransaction' oplog entry.



 Comments   
Comment by Githook User [ 08/Oct/18 ]

Author:

{'name': 'Siyuan Zhou', 'email': 'siyuan.zhou@mongodb.com', 'username': 'visualzhou'}

Message: SERVER-37505 Run applyOps with prepare: true in its own batch in MultiApplier.
Branch: master
https://github.com/mongodb/mongo/commit/d753adf541a85c152fa0db90432accfce3d49676

Comment by Siyuan Zhou [ 07/Oct/18 ]

schwerin, yes, until we do SERVER-35880 to make it in parallel. Updated the description.

Comment by Andy Schwerin [ 07/Oct/18 ]

This is temporary, right? The description doesn’t indicate.

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