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

rs.initiate allows the creation of a non-capped oplog

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • 3.0.7, 3.1.9
    • None
    • Replication
    • None
    • Replication
    • ALL
    • Hide

      Start a member with --replSet foo
      Run:

      db.getSiblingDB("local").oplog.rs.insert({x:1})
      		 
      rs.initiate()

      Show
      Start a member with --replSet foo Run: db.getSiblingDB("local").oplog.rs.insert({x:1}) rs.initiate()

    Description

      Currently, if you create the local.oplog.rs collection prior to running rs.initiate, you can create a replset that has an unbounded oplog.

      Ideally we should either prevent this, alert (and potentially fail) when running rs.initiate() and a non-capped oplog.rs is found.

      And potentially have a preflight check when starting as a repl member, then alerting and hanging until a resolution is found.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-20858 Invariant failure in OplogStones for non-capped oplog creation

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-22030 Abort if oplog is uncapped when starting in repl mode

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              david.hows David Hows
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: