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

There should be a rather clear way to check the repair's progress

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • None
    • None
    • Logging

    Description

      Currently there is no good way to check the repair's progress, which easily takes hours for reasonably large databases.

      While it is possible to get an idea of the progress by monitoring the data files allocations (the only thing mongod reports during the repair), it is quite inconvenient and rough indicator.

      We should print at least a number of bytes written or a number of documents written out of total (e.g. taken from the collection stats).

      Attachments

        Issue Links

          is related to

          Task - A task that needs to be done. TOOLS-938 The "mongodump --repair" command should have a clear progress indicator

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. WT-6771 The log should clarify what the figures reported during repair mean

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-24618 Progress update in currentOp for repairDatabase

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              brian.lane@mongodb.com Brian Lane
              dmitry.ryabtsev@mongodb.com Dmitry Ryabtsev
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: