Uploaded image for project: 'MongoDB CLI Tools'
  1. MongoDB CLI Tools
  2. TOOLS-434

Improve error messages when using mongodump --oplog against standalone and sharded

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0.0
    • Component/s: None
    • Labels:
      None

      Description

      Right now, if you run mongodump --oplog against a standalone you get a pretty unhelpful error:

      ```
      error getting oplog start: not found
      ```

      When you run against a sharded cluster, you get a slightly more helpful error message, but still should be better IMO

      ```
      error getting oplog start: can't use 'local' database through mongos
      ```

      Might be worth telling the user to make sure they're running mongodump --oplog against a repl set in the "error getting oplog start" message

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              valeri.karpov Valeri Karpov
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: