Uploaded image for project: 'MongoDB Database Tools'
  1. MongoDB Database Tools
  2. TOOLS-938

The "mongodump --repair" command should have a clear progress indicator

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: mongodump
    • None

      Currently "mongodump --repair" reports a number of documents written for each extent:

      2015-08-23T09:26:58.318+1000 wrote 8839 documents
      2015-08-23T09:26:58.319+1000 extent loc: 0:d1000
      2015-08-23T09:26:58.320+1000 length:2097152
      2015-08-23T09:26:58.327+1000 wrote 2186 documents
      2015-08-23T09:26:58.329+1000 extent loc: 0:51000
      2015-08-23T09:26:58.330+1000 length:524288
      2015-08-23T09:26:58.332+1000 wrote 539 documents
      2015-08-23T09:26:58.332+1000 extent loc: 0:31000
      2015-08-23T09:26:58.333+1000 length:131072
      

      As the repair process may take ages for reasonably large database, we should have a clear indicator of progress - e.g. number of bytes processed out of total, or number of documents processed out of total.

            Assignee:
            david.golden@mongodb.com David Golden
            Reporter:
            dmitry.ryabtsev@mongodb.com Dmitry Ryabtsev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: