Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | SERVER-41772 Apply clang-format 7.0.1 to the codebase | clang-format-7.0.1 | 2019-07-27 | 1 | -123/+126 |
| | |||||
* | SERVER-40386: assert responses of abortTransaction_forTesting() and ↵ | Lingzhi Deng | 2019-06-01 | 1 | -1/+1 |
| | | | | commitTransaction_forTesting() | ||||
* | SERVER-39516 Use database MODE_IX lock for creating collection | Xiangyu Yao | 2019-04-18 | 1 | -6/+0 |
| | |||||
* | SERVER-40502 Turn off failpoint before shutting down test in ↵ | Vesselina Ratcheva | 2019-04-08 | 1 | -0/+3 |
| | | | | ddl_ops_after_prepare_lock_failpoint.js | ||||
* | SERVER-39074 All operations enforce prepare conflicts by default | Louis Williams | 2019-03-19 | 1 | -2/+8 |
| | | | | | | | | | | | | 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-40038 Handle renames across databases in lock failpoint. | Max Hirschhorn | 2019-03-08 | 1 | -1/+8 |
| | |||||
* | SERVER-39154 Create a fail point to make it so if a LockManager lock cannot ↵ | Vesselina Ratcheva | 2019-03-04 | 1 | -0/+124 |
be acquired immediately, then the operation fails |