| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Includes SERVER-40084, stores global lock acquisition flag in an
atomic.
|
|
|
|
| |
This reverts commit d99db775dbf73e27bd20e402f26f068dc199203d.
|
|
|
|
|
| |
Includes SERVER-40084, stores global lock acquisition flags in an
atomic.
|
|
|
|
| |
than using a whitelist
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
This reverts commit 0cdb86f3cf2bbabe448669598c32297f5ec8214f.
|
| |
|
|
|
|
|
|
| |
Remove leading comments that are just stating the filename.
Move any file-level comments below the copyright banner.
Remove leading blank lines.
|
|
|
|
| |
parameter “closeConnectionsOnStepdown”.
|
|
|
|
| |
This patch adds functionality for "speculative" majority reads. These are reads that can satisfy "majority" read concern guarantees without support from the storage engine for reading from a historical snapshot. Queries of this nature will, by default, wait on the most recent lastApplied optime to majority commit after they complete, but before returning to the client. They can also optionally set a custom optime T to wait on, if they know that they did not read any data that reflects the effects of operations newer than optime T.
|
|
|
|
| |
compatibility
|
| |
|
|
|
|
| |
for embedded.
|
|
|
|
| |
embedded build
|
|
|
|
|
|
| |
Adds a new 'MaxTimeMSExpired' error code, returned when a timeout occurs
due to exceeding of maxTimeMS. Timeouts unrelated to maxTimeMS will
continue to return 'ExceededTimeLimit'.
|
|
|
|
|
|
|
|
|
|
| |
All remaining callers are transitioned to some form of usassert. This was done
with an elaborate set of vim macros to make this tractable. Therefore it
should not be considered an example of the best way to write new code, just as
an improvement on what was there before. In particular, I couldn't easily
remove Status's that are named then only used once in uassertStatusOK, nor
could I convert the pattern of checking a StatusWith<T>'s getStatus() then
calling getValue() to just call uassertStatusOK(returnsStatusWith()).
|
|
|
|
|
|
|
|
|
| |
* Added appendCommandStatusNoThrow matching the current aCS behavior
* Make appendCommandStatus call uassertStatusOK then aCS on success
* Make the few places that need to not throw call aCSNT
A following commit will completely remove appendCommandStatus. It is split out
because that commit is fairly huge.
|
| |
|
|
|
|
| |
This reverts commit 76bc4f800ba2a103d67fa4600d3946f255927818.
|
| |
|
|
|
|
| |
...rather than a whitelist of names maintained in commands.h.
|
|
|
|
|
|
| |
Revert "Revert "SERVER-33065 CommandReplyBuilder and CommandInvocation""
This reverts commit 74177edb35b6ce7594e4751051010ceade592484.
Leave out the unintentional repl/ change this time.
|
|
|
|
| |
This reverts commit ad94e51e0dd40b0d0c38215a36caf75a4be48415.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
remove publicRun from mr_test.cpp
change explain to take OpMsgRequest
private explain
private allowsAfterClusterTime
private supportsWriteConcern supportsReadConcern
remove publicRun
cluster_explain_cmd.cpp: do not inject "$db" field.
let explain() exceptions escape
update cluster distinct explain
|
|
|
|
|
|
|
|
| |
common base for service_entry_point_embedded and
service_entry_point_mongod.
Use the deps of service_entry_point_embedded as
a starting point for the deps of service_entry_point_common.
|
|
|
|
| |
getting interfaces without using global get function.
|
|
|
|
|
|
|
| |
OperationContext
The OperationContext was previously used to retrieve the rollback ID from the
ReplicationProcess.
|
| |
|
|
|
|
| |
This reverts commit d6ad188cd77fb4fcd155cf2c9165fad9e6f2c589.
|
| |
|
|
|
|
| |
New shim libraries to check fsync write lock and repair database on mmapv1 to break dependency chain.
|
| |
|
| |
|
|
|
|
|
|
| |
w/fix: update a new command to secondaryAllowed
This reverts commit d75cb425fbc3cf4b569eb1722c3f8abec45654a2.
|
|
|
|
| |
This reverts commit be24b0323d3f2d424d9e22337f4221d39001ac31.
|
|
|
|
| |
declare read_preference dep. update service_entry_opint_embedded
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
support document-level locking
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Removes the initialClusterTime and initialOperationTime session
options.
* Enables causal consistency by default when using an explicit
session.
* Adds a --retryWrites command line option to the mongo shell for
enabling retryable writes in the mongo shell. The retryWrites
options to SessionOptions is left for convenience with testing.
* Renames setClusterTime() to advanceClusterTime(), and adds a
corresponding advanceOperationTime() method to DriverSession.
* Enables assigning transaction numbers for write commands where
ordered=false.
* Prevents the mongo shell from sending afterClusterTime or assigning
transaction numbers when talking to a stand-alone mongod.
* Prevents the mongo shell from assigning transaction numbers when
using an unacknowledged (w=0) writeConcern.
* Changes DBClientRS to re-discover the current primary of the replica
set when it receives an error code representing "not master" in
addition to an error message representing "not master".
* Adds a shellPrint() pretty-printer for SessionOptions and
DriverSession instances so they no longer print out their entire
object definition.
|
| |
|
| |
|
| |
|