Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-83460

Investigate if initial sync no longer needs to set the forceBatchBoundaryAfter batching option

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

       

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            wenbin.zhu@mongodb.com Wenbin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: