Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13246

Investigate changes in SERVER-44476: Include number of jumbo chunks remaining in output of removeShard

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.3.3, 4.2.2, 4.0.14
    • manual, Server
    • None

    Description

      Description

      Downstream Change Summary

      There is a new field on the response called "jumboChunks" that returns the total number of jumbo chunks within the shard that needs to be handled manually before being able to remove the shard.

      Description of Linked Ticket

      Currently, if removeShard is called while the shard is still draining the output of the command is

      {
      msg: "draining ongoing",
      state: "ongoing",
      remaining: chunks:5, dbs:1,
      note:"you need to drop or movePrimary these databases dbsToMove"
      }

      The only place the number of jumbo chunks that remains is reported is in the config server logs. It would be more helpful if we also reported this number in the command output as well. We do a find on config.chunks in order to report the number of chunks remaining, so it should be easy to search for those entries which have 'jumbo: true'.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Attachments

        Issue Links

          Activity

            People

              kay.kim@mongodb.com Kay Kim (Inactive)
              backlog-server-pm Backlog - Core Eng Program Management Team
              Jess Mokrzecki Jess Mokrzecki
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                3 years, 40 weeks, 5 days ago