Inconsistent and unhelpful error messages when a db is dropped in middle of mongodump

XMLWordPrintableJSON

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

      On standalone and replica set you get a somewhat confusing message:

      error reading from db: Exec error: PlanExecutor killed

      On sharded cluster, you get something even less useful:

      error reading from db: failed on : shard0001

      We should improve this. Should mongodump even fail at all if underlying db is dropped?

            Assignee:
            Unassigned
            Reporter:
            Valeri Karpov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: