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

ReplBatcher should recalculate batch limits after oplog is resized via replSetResizeOplog

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Replication
    • Labels:

      Description

      We added support for dynamically resizing the oplog on WiredTiger nodes using the replSetResizeOplog command in SERVER-22766. The ReplBatcher thread calculates the batch limit once based on the oplog size known at the time the thread is spawned. We should look at re-evaluating this batch limit whenever the oplog is resized.

      This came out of a code review on SERVER-31587

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: