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

command to resize capped collection (offline oplog size increase)

XMLWordPrintableJSON

    • Type: Icon: New Feature New Feature
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Replication

      If a mongod is started with a different oplog size, we do a full clone of the db with a new oplog size.
      We warn the user this is slow, and ctrl-c should be safe to kill it.
      it just says "new oplog size detected: will make a new local database. this is a slow operation. to abort the migration, ctrl-c and run again with your old --oplogSize of ___".

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            eliot Eliot Horowitz (Inactive)
            Votes:
            5 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: