[SERVER-83460] Investigate if initial sync no longer needs to set the forceBatchBoundaryAfter batching option Created: 20/Nov/23  Updated: 21/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Wenbin Zhu Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

forceBatchBoundaryAfter was introduced as part of SERVER-41270 to avoid an issue caused by partial transaction oplog entries during initial sync. However today the oplog applier already tracks partial transaction ops in a batch, so it's likely no longer needed to set this option during initial sync.

 


Generated at Thu Feb 08 06:52:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.