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

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

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.0.7, 3.1.9
    • Component/s: 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()

      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.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            david.hows David Hows
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: