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

Prevent incorrectly dropping oplog on 4.0

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Won't Do
    • None
    • None
    • Replication
    • None

    Description

      SERVER-38356 requested adding guardrails to prevent users from dropping the oplog in standalone mode due to the use of an outdated procedure for resizing the oplog. In versions 4.0 and later, dropping the oplog in standalone mode can cause loss of majority-committed writes. The fix banned dropping the oplog completely for storage engines that support the replSetResizeOplog command on versions 4.0 and later, with the suggested workaround to drop the entire local database in cases where dropping the oplog is necessary, such as restoring a replica set backup to a standalone. This was reverted on 4.0 inĀ SERVER-47558 because it prevented some necessary maintenance procedures. We should consider alternative solutions on 4.0 (and perhaps on later branches), such as adding a force option to the drop command, or banning dropping the oplog only when there is a replica set config.

      Attachments

        Issue Links

          Activity

            People

              evin.roesle@mongodb.com Evin Roesle
              tess.avitabile@mongodb.com Tess Avitabile (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: