Details
-
Bug
-
Status: Closed
-
Minor - P4
-
Resolution: Duplicate
-
4.0.0
-
None
-
None
-
ALL
-
Repl 2019-01-14
Description
The run_check_repl_dbhash_background.js script may or may not call commitTransaction before it catches an expected exception and calls abortTransaction. If it does call commitTransaction first, then abortTransaction is prohibited (per spec) and throws a client-side error:
[CheckReplDBHashInBackground:job2:prepare_requires_fcv42:CheckReplDBHashInBackground] 2018-12-21T23:11:11.336+0000 2018-12-21T23:11:11.330+0000 E QUERY [js] Error: Cannot call abortTransaction after calling commitTransaction. :
|
[CheckReplDBHashInBackground:job2:prepare_requires_fcv42:CheckReplDBHashInBackground] 2018-12-21T23:11:11.337+0000 abortTransaction@src/mongo/shell/session.js:788:1
|
[CheckReplDBHashInBackground:job2:prepare_requires_fcv42:CheckReplDBHashInBackground] 2018-12-21T23:11:11.337+0000 abortTransaction_forTesting@src/mongo/shell/session.js:980:24
|
[CheckReplDBHashInBackground:job2:prepare_requires_fcv42:CheckReplDBHashInBackground] 2018-12-21T23:11:11.337+0000 @jstests/hooks/run_check_repl_dbhash_background.js:274:25
|
[CheckReplDBHashInBackground:job2:prepare_requires_fcv42:CheckReplDBHashInBackground] 2018-12-21T23:11:11.337+0000 @jstests/hooks/run_check_repl_dbhash_background.js:18:2
|
Attachments
Issue Links
- duplicates
-
SERVER-38182 run_check_repl_dbhash_background aborts all transactions after an error even if they've already successfully committed
-
- Closed
-