Details
-
Bug
-
Resolution: Done
-
Major - P3
-
2.0.0
-
None
-
Connect to a replica set secondary and try running the compact command on a non-existent collection. You'll get an assertion, and the node will stay in recovery mode.
-
ALL
Description
Connect to a replica set secondary and try running the compact command on a non-existent collection. You'll get an assertion, and the node will move to and remain in a recovery state. You want to node to remain in secondary state, but the only way to fix this is to run compact again on a valid collection.
Attachments
Issue Links
- is depended on by
-
SERVER-4329 uncaught exception in mapreduce causes mongod to terminate
-
- Closed
-
- is duplicated by
-
SERVER-4210 Compact that even failed to start leaves server in "RECOVERING" state
-
- Closed
-