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

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Logging
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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).

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

              Created:
              Updated:
              Resolved: