If during the cloning of collections the database is dropped then it is possible that none of the collections are copied – same can happen with a collection as well. If we then apply an operation from the oplog which tries to change that collection, like collMod, it is possible for it fail and error (causing a shutdown of the server).
We should write a test to reproduce this before we attempt a fix, to ensure it is a real problem.
One possible solution might be that we check if the collection still exists remotely and if not, ignore the error – since the database will be dropped later in the oplog.
- is related to
-
SERVER-20677 Failed collMod during replication results in fassert shutdown
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-