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

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

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 3.0.9
    • Component/s: Replication
    • None
    • Environment:
      Amazon Linux
    • Linux

      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.

        1. mms.png
          mms.png
          460 kB

            Assignee:
            Unassigned Unassigned
            Reporter:
            amanpreet@codigami.com Amanpreet Singh
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: