Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-12542

Reclaiming space after resizing Oplog

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Minor - P4 Minor - P4
    • Server_Docs_20231030
    • 3.6
    • manual, Server
    • None

    Description

      Description

      The documented procedure to "Compact oplog.rs to reclaim disk space" might be improved on a couple points.

      1. It implies, but does not make crystal-clear, that the compact operation must be performed only on SECONDARY members. I am working now with a customer who has been confused by this. (00551858)
      2. The recommended step rs.stepDown() may not always work as expected in replica sets with asymmetric priorities. In a P-S-S with priorities 5, 2, and 1, when you `stepDown()` the primary, it will quickly initiate a priority-takeover, and "step back up".

      Scope of changes

      • Specify in first paragraph that you must run compact against secondaries only
      • Revise rs.stepdown to specify a stepdown timeout of 120 seconds (to ensure a high-priority primary does not immediately re-elect itself)

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Attachments

        Activity

          People

            Unassigned Unassigned
            mark.brinsmead@mongodb.com Mark Brinsmead
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              1 year, 14 weeks, 2 days ago