More informative error message when server crashes while mongodump is running

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None

      Right now message is:

      error reading from db: EOF

      The `error reading from db:` comes from mongodump, and the EOF is stringified because mgo returns `io.EOF` when server crashes instead of an error. Maybe we should check if mgo error equals `io.EOF` and, if so, say that we couldn't reach the server?

              Assignee:
              DO NOT USE - Backlog - Platform Team
              Reporter:
              Valeri Karpov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: