summaryrefslogtreecommitdiff
path: root/jstests/replsets/recover_prepared_transaction_state.js
Commit message (Collapse)AuthorAgeFilesLines
* SERVER-55676 [SBE][replica_sets] Tests trigger fatal assertion: ↵Mindaugas Malinauskas2021-04-141-1/+0
| | | | NotPrimaryOrSecondary: Oplog collection reads are not allowed while in the rollback or startup state
* SERVER-55009 enable replica_sets for SBE build variantKyle Suarez2021-04-061-1/+5
|
* SERVER-47877 Replace uses of arrayEq without assert with assert.sameMembers ↵Matthew Russotto2020-05-061-4/+3
| | | | in replsets tests
* SERVER-41772 Apply clang-format 7.0.1 to the codebaseclang-format-7.0.12019-07-271-167/+164
|
* SERVER-40386: assert responses of abortTransaction_forTesting() and ↵Lingzhi Deng2019-06-011-1/+1
| | | | commitTransaction_forTesting()
* SERVER-40469 Remove expectPreparedTxnsDuringRollback option.Max Hirschhorn2019-05-241-3/+2
|
* Revert "SERVER-41079 Add new build variant for the multiple oplog entries ↵Jason Chan2019-05-161-1/+1
| | | | | | transaction format" This reverts commit 6df77aa1579d11894a80ddd2edb3053db5abd0aa.
* SERVER-41079 Add new build variant for the multiple oplog entries ↵Jason Chan2019-05-161-1/+1
| | | | transaction format
* SERVER-40482 SERVER-40517 Fix fastcount algorithm for rollback of prepared ↵Louis Williams2019-04-121-5/+9
| | | | | | | | | | | | | | | | | | | transactions This fixes two bugs, both related the correctness of the algorithm for adjusting collection counts during rollback. The first bug is that rolled-back non-majority confirmed "prepare" oplog entries may rollback and incorrectly adjust collection fastcounts. The second bug is that a prepared and committed transaction will have incorrect collection counts after rollback. The new high-level order of operations during replication rollback are as follows: 1. Abort all active prepared transactions, rolling back any in-memory counts 2. Calculate collection count adjustments by scanning rolled-back oplog entries 3. If a 'commitTransaction' oplog entry is rolled-back, find the associated 'prepare' to calculate size adjustments 4. Rollback to the stable timestamp. Replay oplog to common point. This makes no collection count adjustments. 5. Set collection counts to previously calculated values 6. Reconstruct prepared transactions, which updates in-memory fastcounts
* SERVER-39689 add data consistency parameters to rollback_testPavi Vetriselvan2019-04-101-1/+1
|
* SERVER-40269: commitTransaction should assert that the prepare oplog entry ↵Lingzhi Deng2019-04-091-13/+15
| | | | is majority committed
* Revert "SERVER-35811 disallow committing at the prepareTimestamp and pin ↵Pavi Vetriselvan2019-04-011-1/+1
| | | | | | stable TS before oldest uncommitted TS" This reverts commit b58420e57a2149c350ebf82815fe708850402296 and 33ac1afd4079e04d12554f9b79d1ab07426caf59.
* SERVER-39762 Fix fastcount after rollback recovery of prepared transactionsLouis Williams2019-03-271-5/+16
|
* SERVER-39074 All operations enforce prepare conflicts by defaultLouis Williams2019-03-191-0/+1
| | | | | | | | | | | | Prepare conflicts may only be safely ignored when a command can guarantee it does not perform writes. Prepare conflicts are ignored when the read concern is local, available, or majority and the command is aggregate, count, distinct, find, getMore, or group. Aggregate is a special case because it may perform writes to an output collection, but it enables prepare conflict enforcement before doing so. Additionally, connections from a DBDirectClient inherit the ignore_prepare state from their parent operation.
* SERVER-39910 Fix race in rollback_drop_database.jsA. Jesse Jiryu Davis2019-03-081-6/+4
|
* SERVER-35872 reconstruct prepared transactions on rollback, fastcount inaccuratePavi Vetriselvan2019-02-221-0/+184
View Lorry Controller Status