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

test that secondaries roll over their oplogs when they exceed oplogSize

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.11
    • Component/s: Replication
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Repl 2019-04-22, Repl 2019-05-06

      Description

      In the absence of transactions, we don't have testing that secondaries roll over their oplogs when they exceed oplogSize.

      This is specifically to test that work in SERVER-36494 did not prevent storage engines that do not support transactions from truncating their oplogs when transactions are not in use (ex: inMemory).

      This can likely be built on top of initial_sync_oplog_rollover.js or the tests added in SERVER-36494.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              lingzhi.deng Lingzhi Deng
              Reporter:
              judah.schvimer Judah Schvimer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: