-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
ALL
-
During the training, scotthernandez managed to drop the oplog on a slaveDelay secondary that was currently active with:
db.getSiblingDB("local").oplog.rs.drop()
db.getSiblingDB("local").oplog.rs.stats()
Now returns:
{ "ok" : 0, "errmsg" : "ns not found" }
- is duplicated by
-
SERVER-14222 Replica set members should disallow dropping local.oplog.rs
- Closed
- is related to
-
SERVER-13483 segmentation fault after dropping oplog
- Closed
- related to
-
SERVER-11383 Prevent copydb to/from local database
- Closed