mirrors/mongodb
mirrors/mongodb
0
0
Fork 0
mirror of https://github.com/mongodb/mongo.git synced 2024-12-01 09:32:32 +01:00
Code Issues Releases Activity

SERVER-38961 rollback_via_refetch_survives_nonexistent_collection_drop.js does not need to wait for rollback to finish before searching logs

Browse Source
This commit is contained in:
Benety Goh 2020-05-02 07:22:21 -04:00 committed by Evergreen Agent
parent f002800003
commit 0eb06f28fd
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
jstests/replsets/rollback_via_refetch_survives_nonexistent_collection_drop.js
View File

@ -60,12 +60,13 @@ jsTestLog("Turning off the rollbackExitEarlyAfterCollectionDrop fail point");
assert.commandWorked(rollbackDB.adminCommand(
{configureFailPoint: 'rollbackExitEarlyAfterCollectionDrop', mode: 'off'}));
rollbackTest.transitionToSteadyStateOperations();
// After a successful rollback attempt, we should have seen the following log message to ensure
// that we tried to drop a non-existent collection and continued without acquiring a database
// lock.
checkLog.contains(rollbackDB.getMongo(), "This collection does not exist");
// lock. This check has to be before transitionToSteadyStateOperations() to make sure ram logs
// are not overwritten due to oplog fether retry error.
checkLog.containsJson(rollbackDB.getMongo(), 21696); // This collection does not exist
rollbackTest.transitionToSteadyStateOperations();
rollbackTest.stop();
}());
}());