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

Disable the ability to run defragmentCollection on collections with active defragmentation

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Minor - P4 Minor - P4
    • None
    • None
    • None
    • None
    • Sharding EMEA

    Description

      Today a customer can run the following command to defragment a collection on a collection that is already being defragmented.

      db.adminCommand({configureCollectionBalancing: "<database>.<collection>",  defragmentCollection: true}) 

      This behavior is unintended and could allow a customer to input a different chunkSize (example below)

      db.adminCommand({configureCollectionBalancing: "<database>.<collection>", defragmentCollection: true, chunkSize: 64})  

      By altering the chunkSize on a collection that is already being defragmented could lead to improper or less than ideal behavior. So a customer should not be able to successfully run a command to start defragmentation on a collection that is being actively defragmented.

      Attachments

        Activity

          People

            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            matt.panton@mongodb.com Matt Panton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: