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

oplog drops to zero unexpectedly

XMLWordPrintableJSON

    • Type: Icon: Question Question
    • Resolution: Incomplete
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 4.2.3
    • Component/s: Replication
    • Labels:
      None
    • Minor Change

      On a single Secondary node of a replica set, after resizing a 1+ TB oplog a total of three (3) times (-> 51200 MB -> 25600 MB -> 5120 MB), the oplog dropped to zero/empty, and the mongod log shows no indication of having restarted.

      Please help us understand why the oplog unexpectedly became empty.

            Assignee:
            Unassigned Unassigned
            Reporter:
            barry.johnson@mongodb.com Barry Johnson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: