[SERVER-26932] Further improve index_retry.js, index_no_retry.js, and crashAfterStartingIndexBuild failpoint Created: 07/Nov/16  Updated: 06/Dec/22  Resolved: 16/Sep/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Max Hirschhorn Assignee: Backlog - Storage Execution Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-23510 Fix index_retry.js and index_no_retry... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

1. Avoid letting the server continue running if RecoveryUnit::waitUntilDurable() return false.

if (MONGO_FAIL_POINT(crashAfterStartingIndexBuild)) {
    log() << "Index build interrupted due to 'crashAfterStartingIndexBuild' failpoint. Exiting "
             "after waiting for changes to become durable.";
    Locker::LockSnapshot lockInfo;
    _txn->lockState()->saveLockStateAndUnlock(&lockInfo);
    if (_txn->recoveryUnit()->waitUntilDurable()) {
        quickExit(EXIT_TEST);
    }
}

2. Inline the contents of the abortDuringIndexBuild() function and eliminate the unnecessary usage of startParallelShell() in index_retry.js and index_no_retry.js. The changes from SERVER-23510 made it so that creating the background index should synchronously crash the server, so the tests no longer need to use multiple clients.


Generated at Thu Feb 08 04:13:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.