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

command to resize capped collection (offline oplog size increase)

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication, Storage
    • Labels:
      None
    • Case:

      Description

      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 ___".

        Attachments

          Issue Links

          duplicates

          New Feature - A new feature of the product, which has yet to be developed. SERVER-22766 Dynamic oplog sizing for WiredTiger nodes

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-3878 We do not allow resizing (drop+create) of system capped collections (profile) on secondaries

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: