On v5.0, when using recoverFromOplogAsStandalone, after recovering from the oplog we set the internal readOnly flag to true. If also using startupRecoveryForRestore, we have also advanced the oldest timestamp during the oplog application, as described in SERVER-55766. This means that the drop-pending ident reaper will run, dropping any tables from a collection drop applied during the recovery. Then when we go to drop the ident, we can run into an IllegalOperation error because the readOnly flag is set.
- causes
-
SERVER-84432 mongod crashes on start with --recoverFromOplogAsStandalone
-
- Closed
-
- is caused by
-
SERVER-55766 Introduce an optimized "for restore" startup replication recovery mechanism
-
- Closed
-
- is related to
-
-
- Closed
-