summaryrefslogtreecommitdiff
path: root/src/mongo/db/repl/storage_interface_impl.cpp
Commit message (Collapse)AuthorAgeFilesLines
* SERVER-39679 Get oldest transaction time when snapshottingA. Jesse Jiryu Davis2019-03-211-1/+1
|
* SERVER-39765 Rename `exec/update.{h,cpp}` to `exec/update_stage.{h,cpp}`Kaloian Manassiev2019-02-221-1/+1
|
* SERVER-39560 - remove leading blank line on all C++ filesBilly Donahue2019-02-131-1/+0
| | | | | | Remove leading comments that are just stating the filename. Move any file-level comments below the copyright banner. Remove leading blank lines.
* SERVER-37283 Use stronger locks for system.viewsCharlie Swanson2019-02-111-2/+6
| | | | | | | | | | Readers of the view catalog depend on a MODE_IS DB lock preventing concurrent writes to the view catalog. This is true for regular view maintenance commands like collMod, create, and drop. However, on secondaries these commands are replicated as direct writes to system.views and do not hold as strong of a lock. Further, a user is permitted to write directly to system.views and so could hit a similar issue on the primary.
* SERVER-38316 Consolidate PlanExecutor::DEAD and PlanExecutor::FAILUREPawel Terlecki2019-02-041-1/+0
| | | | | Takes care of PlanExecutor states. In some cases we log more information for former DEAD state scenarios now.
* Revert "SERVER-38527 Merge supportsRecoverToStableTimestamp into ↵Gregory Wlodarek2019-01-231-1/+5
| | | | | | supportsRecoveryTimestamp" This reverts commit b54951b484b2cba44ffa424f43acb870365e3f12.
* SERVER-38179 range deleter must be prepared for document to be deleted from ↵Randolph Tan2019-01-111-4/+4
| | | | under it
* SERVER-38527 Merge supportsRecoverToStableTimestamp into ↵Gregory Wlodarek2019-01-101-5/+1
| | | | supportsRecoveryTimestamp
* SERVER-38479 allow lock acquisition interruptions in ↵Eric Milkie2019-01-071-2/+1
| | | | StorageInterface::createCollection and dropCollection
* Revert "SERVER-38527 Merge supportsRecoverToStableTimestamp into ↵Gregory Wlodarek2019-01-041-1/+5
| | | | | | supportsRecoveryTimestamp" This reverts commit 804617152c5b4f89c8d54c83bdea90cb2c8541b4.
* SERVER-38527 Merge supportsRecoverToStableTimestamp into ↵Gregory Wlodarek2019-01-031-5/+1
| | | | supportsRecoveryTimestamp
* SERVER-38719 rename DatabaseHolder::get() to getDb()Benety Goh2018-12-201-3/+3
| | | | | Repurpose DatabaseHolder::get() for accessing singleton. Deprecate DatabaseHolder::getDatabaseHolder().
* SERVER-38700 fold dropAllDatabasesExceptLocal logic into ↵Benety Goh2018-12-191-2/+32
| | | | | | StorageInterfaceImpl::dropReplicatedDatabases This function is used during initial sync only.
* SERVER-38091 IndexCatalog iterators and accessors should return const entriesLouis Williams2018-12-191-2/+2
|
* SERVER-34620 Make speculative read atClusterTime not wait for the given ↵Matthew Russotto2018-12-061-1/+5
| | | | cluster time to be majority-committed
* SERVER-35449 Return the oldest read timestamp used by any open transactionJason Chan2018-11-291-0/+4
|
* SERVER-38033 Fix CollectionImpl::_ns thread safety.David Storch2018-11-141-5/+0
|
* SERVER-37446 Make UPDATE and DELETE inherit from RequiresMutableCollectionStage.David Storch2018-11-121-7/+0
| | | | | Also deletes UpdateLifecyle, which was used as part of the UpdateStage's yield recovery, but is no longer necessary.
* SERVER-37179 Pull out starting transaction from session checkout and push it ↵Siyuan Zhou2018-11-081-0/+6
| | | | | | | | 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-36889 unshim MultiIndexBlockBenety Goh2018-10-121-1/+0
|
* SERVER-37227 Reintroduce enableMajorityReadConcern:false server parameterTess Avitabile2018-10-021-0/+4
|
* SERVER-36811: Save oplog dating back to oldest actively prepared transaction.Daniel Gottlieb2018-09-171-1/+1
|
* SERVER-37048 Hold global intent lock whenever accessing the oplog collection ↵Spencer T Brody2018-09-101-2/+4
| | | | pointer
* SERVER-35860 Maintain multikey metadata keys for allPaths indexesBernard Gorman2018-08-091-0/+7
|
* SERVER-35367 Do not hold locks while calling ↵Spencer T Brody2018-07-311-2/+11
| | | | waitForAllEarlierOplogWritesToBeVisible()
* SERVER-36101 Replication should not depend on the presence of ↵Dianna Hohensee2018-07-251-2/+14
| | | | lastStableCheckpointTimestamp in status reports to identify recoverable rollback capable nodes
* SERVER-34615 Make UUIDCatalog updates for renameCollection atomicMaria van Keulen2018-06-061-2/+1
|
* SERVER-32825 Add upgrade/downgrade infrastructure for timestamp safe unique ↵nehakhatri52018-05-181-0/+4
| | | | | | index. This change is currently guarded by a gating variable.
* SERVER-34895 only set stable timestamp to timestamps in oplogJudah Schvimer2018-05-151-0/+8
|
* SERVER-34967 Handle PlanExecutor failure in StorageInterfaceImplCharlie Swanson2018-05-151-98/+108
|
* SERVER-34751 Replace getGlobalStorageEngine cals with getStorageEngine.Andy Schwerin2018-05-031-6/+6
|
* SERVER-32645 Create a shim helper framework.ADAM David Alan Martin2018-04-301-1/+1
| | | | | | | | The `MONGO_DECLARE_SHIM`, `MONGO_DEFINE_SHIM`, and `MONGO_REGISTER_SHIM` macros can be used to create specialized types which are customization and auto-registration points for late-binding functions. In some sense they work like weak-symbols; however, they also are useful for tracking dependencies upon shimmed-out implementations.
* Revert "SERVER-32645 Create a shim helper framework."Kyle Suarez2018-04-301-1/+1
| | | | This reverts commit 2227f272a7a0a3e43625cb2d4a2704e1ccb6f893.
* SERVER-32645 Create a shim helper framework.ADAM David Alan Martin2018-04-271-1/+1
| | | | | | | | The `MONGO_DECLARE_SHIM`, `MONGO_DEFINE_SHIM`, and `MONGO_REGISTER_SHIM` macros can be used to create specialized types which are customization and auto-registration points for late-binding functions. In some sense they work like weak-symbols; however, they also are useful for tracking dependencies upon shimmed-out implementations.
* SERVER-33349 Add command to get stable checkpoint timestampJudah Schvimer2018-04-101-0/+15
|
* SERVER-33493 Have WT RTT rollback keep correct countsJudah Schvimer2018-03-291-3/+23
|
* SERVER-29213: Have WiredTiger support recoverToStableTimestamp.Daniel Gottlieb2018-03-241-2/+2
|
* SERVER-33846: Set oplog visibility synchronously on secondaries, at the end ↵Daniel Gottlieb2018-03-151-0/+8
| | | | | | | | | | | | | | | | | | | 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-43/+50
| | | | | | | | | | | | | | 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/+10
| | | | playing oplog from
* SERVER-29519 Remove getGlobalReplicationCoordinator. Replace when getting ↵Nick Zolnierz2018-03-021-1/+0
| | | | | | decoration through service context (global if needed). This reverts commit a8fddd07a740e959646995ef93139887b3b3eb5c.
* Revert "SERVER-29519 Remove getGlobalReplicationCoordinator. Replace when ↵Nick Zolnierz2018-03-021-0/+1
| | | | | | getting decoration through service context (global if needed)." This reverts commit 7d37a75df3f6035a7afcb51123b88f0e99308fc8.
* SERVER-29519 Remove getGlobalReplicationCoordinator. Replace when getting ↵Henrik Edin2018-03-021-1/+0
| | | | decoration through service context (global if needed).
* SERVER-32272 Remove 3.4 to 3.6-specific UUID handlingMaria van Keulen2018-03-011-4/+0
|
* SERVER-32638 Rename interruptable to interruptibleLouis Williams2018-03-011-2/+2
|
* SERVER-32638: Allow lock acquisition to be interruptableLouis Williams2018-03-011-0/+2
|
* SERVER-33496: Stop timestamping collection drops.Daniel Gottlieb2018-02-281-4/+0
|
* SERVER-32206 timestamp catalog change to declare index multikeyJudah Schvimer2018-02-021-0/+40
|
* SERVER-32251: Timestamp drop collection/databaseDaniel Gottlieb2018-01-241-0/+5
|
View Lorry Controller Status