Details
-
Task
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
-
Replication
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.