Commit Graph

9 Commits

Author SHA1 Message Date
Moustafa Maher 0d97b04197 SERVER-55703 Update getDefaultRWConcern 2021-04-29 23:07:54 +00:00
Mindaugas Malinauskas 4c166a537d SERVER-55676 [SBE][replica_sets] Tests trigger fatal assertion: NotPrimaryOrSecondary: Oplog collection reads are not allowed while in the rollback or startup state 2021-04-14 15:29:00 +00:00
Kyle Suarez 18081d9a21 SERVER-55009 enable replica_sets for SBE build variant 2021-04-06 13:46:03 +00:00
Cheahuychou Mao fd7aaa92a2 SERVER-44310 Make waitForFailPoint command require maxTimeMS 2019-10-31 13:35:41 +00:00
Cheahuychou Mao 99d90208c6 SERVER-39165 Add waitForFailpoint command and update initial sync tests 2019-10-25 18:52:44 +00:00
clang-format-7.0.1 134a408395
SERVER-41772 Apply clang-format 7.0.1 to the codebase 2019-07-27 11:02:23 -04:00
Pavi Vetriselvan e433a5aee9 Revert "SERVER-35811 disallow committing at the prepareTimestamp and pin stable TS before oldest uncommitted TS"
This reverts commit b58420e57a and 33ac1afd40.
2019-04-01 14:05:19 -04:00
Louis Williams 197233a97c SERVER-39074 All operations enforce prepare conflicts by default
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.
2019-03-19 17:03:40 -04:00
Samy Lanka 4f858c52b0 SERVER-36489 Start initial sync oplog fetching from the 'oldest active transaction timestamp'
SERVER-36490 Initial sync should not actually prepare transactions on applying prepareTransaction oplog entries
SERVER-36491 During initial sync, make commitTransaction oplog entries apply the transaction from the prepare oplog entry
2019-02-11 12:27:33 -05:00