summaryrefslogtreecommitdiff
path: root/src/mongo/db/repl/storage_interface_mock.h
Commit message (Collapse)AuthorAgeFilesLines
* SERVER-58691 Implement deletion of pre-images which corresponding oplog ↵Denis Grebennicov2021-11-101-0/+4
| | | | entry fell off the oplog
* SERVER-57827 Allow putSingleton override in storage_interface_mock.h and ↵ali-mir2021-10-071-1/+7
| | | | maintain initial sync id in replication_consistency_markers_mock.h
* SERVER-57446 fix clang-tidy header issues and add header-filterDaniel Moody2021-08-021-2/+2
|
* SERVER-58385 StorageInterface::setIndexIsMultikey() accepts collection UUIDBenety Goh2021-07-191-0/+1
|
* SERVER-57532 Use donor specs for _id index in tenant migration collection clonerVishnu Kaushik2021-06-101-1/+3
|
* SERVER-54005 Prevent oplog history truncation from deleting entries lte to ↵Dianna Hohensee2021-05-041-0/+3
| | | | the oplogTruncateAfterPoint
* SERVER-31540 Remove usages of boost::optional<UUID> from the StorageInterfaceKaloian Manassiev2021-02-241-9/+7
|
* SERVER-49795 Remove 'getOldestOpenReadTimestamp()' from the storage engine ↵Gregory Wlodarek2020-11-131-2/+0
| | | | interface
* SERVER-51387 Assert that the stable timestamp is never set higher than the ↵Gregory Wlodarek2020-11-061-1/+3
| | | | all durable timestamp
* SERVER-50984 Add CollectionPtr to replace usage of const Collection*Henrik Edin2020-09-261-2/+2
| | | | | | | | | | | | It implements a yieldable interface that is used to re-load the Collection pointer from the catalog after a yield that released locks. With lock-free reads and copy-on-write on Collection instances releasing locks without notifying an AutoGetCollection at a higher level may cause its pointers to dangle if a MODE_X writer installs a new Collection instance in the catalog. CollectionPtr should be passed by const reference so a yield can notify all the way up.
* SERVER-47812 Secondaries persist wildcard multikeypaths out of orderBernard Gorman2020-09-121-0/+1
|
* SERVER-50317 Const correct uses of CollectionHenrik Edin2020-09-021-2/+2
| | | | | | Most of the code should only need a const Collection now. AutoGetCollection returns a const Collection by default. There is a placeholder getWritableCollection() interface that will handle the necessary steps we need for lock free reads in the future. Added some operators to AutoGetCollection so it behaves more like a smart pointer.
* SERVER-48845 Implement TenantCollectionClonerVesselina Ratcheva2020-08-121-0/+15
|
* SERVER-48312 Remove support for 'supportsDocLocking = false'Gregory Wlodarek2020-08-041-3/+0
|
* SERVER-47959 JournalFlusher will retry oplog reads on ↵Dianna Hohensee2020-05-061-0/+5
| | | | WriteConflictExceptions caused by a concurrent {full:true} validate command on the oplog collection
* SERVER-45847 Pull JournalFlusher thread out of WT and place it above the ↵Dianna Hohensee2020-03-171-2/+2
| | | | | | | | | | | | storage engine layer. Creating a new storage/control/ directory that contains StorageControl to handle manipulation of independent processes performing actions against the storage engine for higher level code layers. create mode 100644 src/mongo/db/storage/control/journal_flusher.cpp create mode 100644 src/mongo/db/storage/control/journal_flusher.h create mode 100644 src/mongo/db/storage/control/storage_control.cpp create mode 100644 src/mongo/db/storage/control/storage_control.h
* SERVER-45626: Introduce AutoGetOplog for consistent oplog locking rulesLingzhi Deng2020-03-131-2/+1
|
* SERVER-46185 Add StorageInterface utilities for replicate before journaling ↵Dianna Hohensee2020-02-191-0/+9
| | | | changes and use them to simplify replication recovery oplog truncation code.
* SERVER-42165 Replace uses of stdx::mutex with mongo::MutexBen Caimano2019-09-171-2/+2
|
* SERVER-41772 Apply clang-format 7.0.1 to the codebaseclang-format-7.0.12019-07-271-4/+5
|
* SERVER-41861 Replace 'all_committed' with 'all_durable'Gregory Wlodarek2019-07-261-2/+2
|
* SERVER-40168 Pull the OplogTruncaterThread out of WiredTigerKVEngine and put ↵Gabe Villasana2019-07-111-0/+2
| | | | it above the storage layer
* SERVER-39471 Remove unique index FCV upgrade codepathXiangyu Yao2019-07-101-9/+0
|
* SERVER-36194 Remove the deprecated 'lastStableCheckpointTimestamp' field ↵Zach Yam2019-06-251-5/+0
| | | | from replSetGetStatus response in v4.4 dev cycle
* SERVER-40357 expand all calls to MONGO_DISALLOW_COPYINGBilly Donahue2019-03-281-3/+4
| | | | | | | | | | | produced by: hits="$(git grep -n MONGO_DISALLOW_COPYING | cut -d: -f1 )" for f in "$hits"; do sed -i.orig ' s/^\( *\)MONGO_DISALLOW_COPYING(\(.*\));/\1\2(const \2\&) = delete;\n\1\2\& operator=(const \2\&) = delete;/; ' $f done
* SERVER-39680 Save start timestamp in config.transactionsA. Jesse Jiryu Davis2019-03-061-1/+1
|
* SERVER-38891 Fix some `collection_cloner_test` races.ADAM David Alan Martin2019-01-251-50/+48
| | | | | | | The mocks in these tests hold pointers to items on the stack. The mocks are held in background threads, such as executors. If the executor accesses one of those mocks after the stack frame of its creator leaves, the pointer to the stack frame is now invalid.
* Revert "SERVER-38527 Merge supportsRecoverToStableTimestamp into ↵Gregory Wlodarek2019-01-231-0/+4
| | | | | | supportsRecoveryTimestamp" This reverts commit b54951b484b2cba44ffa424f43acb870365e3f12.
* SERVER-38527 Merge supportsRecoverToStableTimestamp into ↵Gregory Wlodarek2019-01-101-4/+0
| | | | supportsRecoveryTimestamp
* Revert "SERVER-38527 Merge supportsRecoverToStableTimestamp into ↵Gregory Wlodarek2019-01-041-0/+4
| | | | | | supportsRecoveryTimestamp" This reverts commit 804617152c5b4f89c8d54c83bdea90cb2c8541b4.
* SERVER-38527 Merge supportsRecoverToStableTimestamp into ↵Gregory Wlodarek2019-01-031-4/+0
| | | | supportsRecoveryTimestamp
* SERVER-34620 Make speculative read atClusterTime not wait for the given ↵Matthew Russotto2018-12-061-1/+2
| | | | cluster time to be majority-committed
* SERVER-35449 Return the oldest read timestamp used by any open transactionJason Chan2018-11-291-0/+3
|
* SERVER-37179 Pull out starting transaction from session checkout and push it ↵Siyuan Zhou2018-11-081-0/+4
| | | | | | | | down to before command execution. Transaction will begin or continue after waiting for read concern. If an error is thrown on starting transaction, it'll be able to wait for write concern if a write concern is specified.
* SERVER-37651 Update header files with new licenseRamon Fernandez2018-10-221-8/+10
|
* SERVER-37227 Reintroduce enableMajorityReadConcern:false server parameterTess Avitabile2018-10-021-0/+4
|
* SERVER-36101 Replication should not depend on the presence of ↵Dianna Hohensee2018-07-251-1/+6
| | | | lastStableCheckpointTimestamp in status reports to identify recoverable rollback capable nodes
* SERVER-32825 Add upgrade/downgrade infrastructure for timestamp safe unique ↵nehakhatri52018-05-181-0/+9
| | | | | | index. This change is currently guarded by a gating variable.
* SERVER-34895 only set stable timestamp to timestamps in oplogJudah Schvimer2018-05-151-0/+7
|
* SERVER-33349 Add command to get stable checkpoint timestampJudah Schvimer2018-04-101-0/+5
|
* SERVER-33493 Have WT RTT rollback keep correct countsJudah Schvimer2018-03-291-1/+7
|
* SERVER-29213: Have WiredTiger support recoverToStableTimestamp.Daniel Gottlieb2018-03-241-1/+1
|
* SERVER-33846: Set oplog visibility synchronously on secondaries, at the end ↵Daniel Gottlieb2018-03-151-0/+6
| | | | | | | | | | | | | | | | | | | of every batch. This patch introduces an optimization to allow secondaries to set their visibility synchronously with oplog application as well as bypassing additional journal flushing meant for primaries. Primaries replicating oplog entries atomically generate a new optime and pass it to the storage engine's oplog record store via the `oplogDiskLocRegister` method. This code path will now pass in a parameter `orderedCommit = false` that alerts the storage engine to maintain the necessary oplog visibility semantics for that write. This is existing behavior, the only difference is the addition of the `orderedCommit` parameter. Secondaries will now also call `oplogDiskLocRegister` at the end of every batch. This call will pass in the optime of the last oplog entry applied and `orderedCommit = true`. A storage engine may take this as a guarantee that there are no oplog holes prior to the input optime.
* SERVER-33873 change StorageInterface methods to accept NamespaceStringOrUUIDKyle Suarez2018-03-151-11/+11
| | | | | | | | | | | | | | This updates the following functions to take a NamespaceStringOrUUID to specify the collection: - insertDocuments - findById - deleteById - upsertById This leaves other methods unchanged; if we decide to keep the StorageInterface around and require more methods to accept a UUID, they could conceivably be updated in a similar manner.
* SERVER-33292 Have storage dictate where replication recovery should begin ↵Judah Schvimer2018-03-121-1/+9
| | | | playing oplog from
* SERVER-32272 Remove 3.4 to 3.6-specific UUID handlingMaria van Keulen2018-03-011-10/+0
|
* SERVER-32206 timestamp catalog change to declare index multikeyJudah Schvimer2018-02-021-0/+9
|
* SERVER-30926 Add timestamps to writes to minValid documentJudah Schvimer2017-12-131-2/+2
|
* SERVER-31662 Initialize rollback id to 1 and log when it changesWilliam Schultz2017-11-281-2/+2
|
* SERVER-31304: Refactor away SnapshotName.Daniel Gottlieb2017-11-211-6/+7
|