-
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,355
-
(copied to CRM)
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?
- backported by
-
TOOLS-2692 [v3.6] mongodump fails when capped collection position lost
-
- Closed
-
- depends on
-
SERVER-12293 initial sync of a capped collection can often fail if highly transient
-
- Backlog
-
-
-
- Backlog
-
- is related to
-
-
- Backlog
-
- related to
-
SERVER-31216 Mark internal collections in metadata so tools don't dump them
-
- Closed
-