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

SERVER-41284 Add failpoint to surface idempotency issues of transaction operations in initial sync

Browse Source
This commit is contained in:
Medha Potluri 2019-07-25 15:42:15 -04:00
parent 9d9c25fffb
commit ce1e63a5a7
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
src/mongo/db/repl/initial_syncer.cpp
View File

@ -110,6 +110,9 @@ MONGO_FAIL_POINT_DEFINE(failAndHangInitialSync);
// Failpoint which fails initial sync before it applies the next batch of oplog entries.
MONGO_FAIL_POINT_DEFINE(failInitialSyncBeforeApplyingBatch);
// Failpoint which fasserts if applying a batch fails.
MONGO_FAIL_POINT_DEFINE(initialSyncFassertIfApplyingBatchFails);
namespace {
using namespace executor;
using CallbackArgs = executor::TaskExecutor::CallbackArgs;
@ -1264,6 +1267,14 @@ void InitialSyncer::_multiApplierCallback(const Status& multiApplierStatus,
stdx::lock_guard<stdx::mutex> lock(_mutex);
auto status =
_checkForShutdownAndConvertStatus_inlock(multiApplierStatus, "error applying batch");
// Set to cause initial sync to fassert instead of restart if applying a batch fails, so that
// tests can be robust to network errors but not oplog idempotency errors.
if (MONGO_FAIL_POINT(initialSyncFassertIfApplyingBatchFails)) {
log() << "initialSyncFassertIfApplyingBatchFails fail point enabled.";
fassert(31210, status);
}
if (!status.isOK()) {
error() << "Failed to apply batch due to '" << redact(status) << "'";
onCompletionGuard->setResultAndCancelRemainingWork_inlock(lock, status);