| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Remove leading comments that are just stating the filename.
Move any file-level comments below the copyright banner.
Remove leading blank lines.
|
| |
|
|
|
|
|
| |
Now that OP_COMMAND is dead, all remaining implementations return the same
BSONObj for data and metadata.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
every unit test.
This patch does several loosely related and surprisingly hard to separate things.
1.) Make the ServiceContext class final
2.) Create a mechanism, called ConstructorActions, for running methods on
ServiceContexts immediately after they're built and immediately before they're
destroyed.
3.) Introduce / improve test fixture base classes for tests, giving them fresh
ServiceContext instances for each test case. There is one fixture for tests that
need a storage engine and another for those that do not.
4.) Make several remaining global variables SC decorations in support of (3)
5.) Replace many MONGO_INITIALIZERS that access getGlobalServiceContext with the
new constructor-actions system, which is needed for (3.)
6.) Fix up tests to use the fixtures from (3) and fix tests that silently used
different service contexts in together in a technically illegal fashion that now
breaks.
7.) Utilize (2) as necessary to simplify initialization of new ServiceContexts,
simplifying the fixtures in (3).
|
| |
|
|
|
|
| |
This reverts commit c5a4250a649ab0afb4ecdf227d4a0400f9e68786.
|
|
|
|
| |
This reverts commit d05e04551b7e399a5554858de48541ae11988b10.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
rollback
|
|
|
|
|
|
| |
startup and rollback"
This reverts commit 8fa770baf8fac6e71a45f84b48eeb3bae96a8dab.
|
|
|
|
| |
rollback
|
|
|
|
| |
replSetInitiate
|
| |
|
|
|
|
| |
ReplicationCoordinatorImpl.
|
|
|
|
|
|
|
| |
This class is intended to hold replication state in a secondary node related to
the copying and applying operations from the sync source.
This initial implementation holds a cached copy of the rollback ID only.
|
|
|
|
| |
This reverts commit fac33fe5a6814169c9c6131d80f1b325c74647da.
|
|
|
|
| |
This reverts commit c08590a6ac9dc54c9d910822d47ea17140b56f89.
|
|
|
|
| |
This reverts commit d0c851e2f4bfea514e22c97af1838640d2849a8c.
|
|
|
|
| |
This reverts commit 7109d453e5a264ba77093b9b068d1eaa056ec837.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This change replaces, wherever possible, references to the concrete
type ReplicationExecutor with references to the interface type
TaskExecutor, and eliminates the repl::ResponseStatus typedef, with an
eye toward eventually replacing ReplicationExecutor with another implementation.
|
| |
|
|
|
|
| |
condition variable in some unit tests.
|
| |
|
|
|
|
| |
Attach logical time metadata to all outgoing messages and process incoming logical time metadata in mongod
|
|
|
|
|
|
| |
This commit is an automated rename of all whole word instances of txn,
_txn, and txnPtr to opCtx, _opCtx, and opCtxPtr, respectively in all
.cpp and .h files in src/mongo.
|
| |
|
|
|
|
| |
distribution
|
|
|
|
|
|
| |
stepdown/stepup
SERVER-27913 Make sure the last applied hash is corresponding to the last applied optime in bgsync start()
|
| |
|
| |
|
|
|
|
| |
methods that will use LogicalClock
|
|
|
|
|
|
|
|
|
|
|
| |
constructors to take owned objects by unique_ptr
The constructors of ReplicationCoordinatorImpl and ReplicationExecutor
predate C++11 support in the MongoDB codebase, and so receive bare
pointers to objects that they actually own. This patch is to changes the
constructors and some of the associated test infrastructure to
transfer ownership by passing unique_ptr, as in more modern
components.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ReplicationCoordinatorImpl
... and simplify ReplCoordTestFixture
ReplicationCoordinatorImpl consults the storage engine's isDurable flag for two purposes:
1. To choose whether to present the durable or applied optime when standing for
election in pv1
2. To decide how to interpret w:majority without an explicit j field when
waiting for write concern.
In the first case, it is unnecessary to choose which optime to apply based on
the isDurable flag. It is always safe and correct to present the applied optime,
because if the node presenting it wins election, it will attempt to commit that
applied optime. That means that voters may safely vote for that node.
In the second case, using the value of the local node's storage engine's
isDurable flag to adjust the meaning of w:majority is out of spec. Whether
w:majority writes wait for journaling is a function only of the
writeConcernMajorityJournalDefault flag when a write concern omits the "j"
field.
This patch removes the unnecessary consultation of the isDurable flag, and
uses the opportunity to simplify the constructor of
ReplicationCoordinatorImpl and its test fixture.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
ReplicationCoordinatorImpl instead of KillOpListener
While this change also improves the readability of _awaitReplication_inlock and
stepDown, it resovles SERVER-26305 by breaking a deadlock cycle caused by the
fact that KillOpListener methods get run under a mutex in ServiceContext.
|
|
|
|
|
|
| |
ReplicationCoordinatorImpl instead of KillOpListener"
This reverts commit 360d6ae39305dbc2f41ca7e0bfd424081fd4f030.
|
|
|
|
|
|
|
|
| |
ReplicationCoordinatorImpl instead of KillOpListener
While this change also improves the readability of _awaitReplication_inlock and
stepDown, it resovles SERVER-26305 by breaking a deadlock cycle caused by the
fact that KillOpListener methods get run under a mutex in ServiceContext.
|
|
|
|
| |
SERVER-23662 Implement "catch-up timeout" configuration variable
|
| |
|