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

Sudden (huge) spike in Oplog GB/hour on primary member

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Duplicate
    • Affects Version/s: 3.0.9
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Environment:
      Amazon Linux
    • Operating System:
      Linux

      Description

      Sudden (huge) spike in Oplog GB/hour on primary member rendered secondaries in "RECOVERY" state. There was no spike in Opcounters, so no idea what went wrong there. Since it's a production db, I wasn't able to wait to collect more information about the issue.

      I have added the relevant MMS graphs. Notice the "Oplog GB/hour". First one is primary member, others are secondaries - all running v3.0.9 WiredTiger.

        Attachments

        1. mms.png
          mms.png
          460 kB

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: