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

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

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 3.0.0
    • Affects Version/s: None
    • Component/s: None
    • None

      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

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

              Created:
              Updated:
              Resolved: