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

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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor - P4 Minor - P4
    • None
    • None
    • None
    • None

    Description

      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?

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: