mongodump fails when capped collection position lost

XMLWordPrintableJSON

    • Type: Investigation
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.2.10
    • Component/s: mongodump
    • None
    • Environment:
      Amazon EC2 instance

      Linux 4.4.8-20.46.amzn1.x86_64 #1 SMP Wed Apr 27 19:28:52 UTC 2016 x86_64 x86_64 GNU/Linux

      mongodump 3.2.10
    • 2
    • 1,590

      mongodump exits with a successful (0) exit status after emitting this message:

      Failed: archive writer: error reading collection: Executor error during find command: CappedPositionLost: CollectionScan died due to position in capped collection being deleted. Last seen record id: RecordId(170604747) / Mux ending but selectCases still open 4

      The database is not fully dumped when mongodump exits.

      The only capped collection is system.profile. The database server is a standalone mongod instance, not in a replica set. The mongodump command line is:

      mongodump -u <user> -p <password> --authenticationDatabase <auth db> --verbose --archive --gzip

      Will this happen with other capped collections, too?

              Assignee:
              Unassigned
              Reporter:
              Bob Lunney
              Votes:
              1 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated: