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

User defined steps to handle out of disk conditions

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • Storage Execution

      When the MongoDB's dbPath has run out of space, no operations are allowed at the MongoD level, such as reads, and new connections are blocked.

      This situation can lead to downtime until the dbPath 's volume is increased in space or a new disk is attached to the system.

      It would be nice to allow the user to have rules in place which would change the behaviour of the MongoD process in the event of an out of disk condition. The user should be allowed to run administrative actions on the MongoD process from the shell. These include deleting databases, collections and documents, as well as attempting a compact.

      These rules, or policies, that the user passes to the MongoD process in advance of this out of disk condition could be something like:

      1. Enable noprealloc
      2. Enable the use of smallfiles
      3. Auto restart the MongoD process, on a different port and with the replSetname ignored or removed
      4. Preform a compaction, drop a database, etc.

      Naturally, this should be logged with a relevant message of what was actually done.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            nick Nick Pellant
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: