| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(cherry picked from commit 0aeb5ce7e8d4a190dac43fd110533eef149f7880)
|
| |
|
|
|
|
| |
(cherry picked from commit 92b698db133f3f0c0f21c4bc0704f1106be3fb62)
|
|
|
|
|
|
| |
pre/post image oplog entry
(cherry picked from commit ee26a6df68dc93e3e66f99180e2d03af09fd9daa)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
mongodb-3.6
ref: b85bcfde3b..bc82f0f038
for: 3.6.3
WT-3766 Lookaside sweep for obsolete updates
WT-3840 Dump more information when data corruption is encountered
WT-3847 Add a stub API for prepared transaction
WT-3854 Remove write lock from commit path, leaving old entries in queue
WT-3866 Bi-weekly WT codebase lint
WT-3875 Collisions in operation tracking map file when a connection is reopened within the same process.
WT-3876 Missing tracking macros cause inaccuracies in operation tracking logs
WT-3877 WT_CONN_EVICTION_NO_LOOKASIDE is cleared unconditionally
WT-3878 Iteration can lose its position when updating a limbo page
WT-3881 key timestamp consistency checking should not check its own updates
WT-3887 log operations in format snapshot-isolation tracking
WT-3888 cursor search-near can return the wrong value for "exact"
WT-3889 Disable test/format key-order check for LSM
WT-3890 core dump walking timestamp queue
WT-3891 Take the sweep walk rwlock whenever removing content from lookaside
WT-3895 Commit timestamp queue getting out of order
|
|
|
|
|
|
| |
sharding_csrs_continuous_config_stepdown_WT suite
(cherry picked from commit fe5b3058c3ba27f8262fa5198cf243053ba50b9b)
|
|
|
|
| |
(cherry picked from commit 984bc43b2e56d9893d3ff92c6a17ab2e2feadf67)
|
|
|
|
| |
(cherry picked from commit a917ca5b1691625d7a1e70e96672386bbf0a6243)
|
|
|
|
| |
(cherry picked from commit 0658fe0f057c7d1b82239c3661619dd9f062a684)
|
|
|
|
| |
This reverts commit 07ba49dc7151e4348892f6f0559a99ab1ea349ab.
|
|
|
|
|
|
| |
individual shards if some shard returned success
(cherry picked from commit f2e168877ab5efb45ec583ca3b4d05a423fe9d54)
|
|
|
|
| |
(cherry picked from commit 72fc7cea722f952e3ad47c5470cb60ae2114097f)
|
|
|
|
|
|
|
|
|
|
|
| |
log entries
with the same timestamps if the operations are coming from multiple shards. When we
resume the change stream we have to position to the right place - the position is determined
both by the timestamp and the document id. Previously we checked the timestamp only,
now we loop over the equal timestamps and find the right document.
(cherry picked from commit 194ec4857fa0db8085da88e22eaae96687902d66)
|
|
|
|
| |
This reverts commit 04600d70a4e4ac85c5f199c5756e0e5acb2a7d05.
|
|
|
|
| |
(cherry picked from commit 3c34eda8d8a38b982a1659b919e9f4b5971ba512)
|
|
|
|
| |
(cherry picked from commit 3220c461b454ce8a8df56a3ca0c72bad79806580)
|
| |
|
|
|
|
| |
(cherry picked from commit d16ce76f69687e34f06eb6db298fa4445d8105dc)
|
|
|
|
|
|
|
|
| |
The PlanEnumerator now tracks pushdown routes which descend
through an $elemMatch object. These routes are pruned when
subsequently descending through an OR.
(cherry picked from commit 17b4094c4d781ffd486b27869f46eea706e490af)
|
|
|
|
| |
(cherry picked from commit bb8ac01f052a7b4b5c042085334ce640a1ab8dd1)
|
|
|
|
|
|
|
| |
Also adds support for using replica set connection strings in resmoke.py
without making all nodes electable.
(cherry picked from commit 264d971842cffdf8b4f80def1d90241f132345b7)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduces OverrideHelpers object with convenience methods for
inspecting certain aggregation and map-reduce commands, as well as
overriding startParallelShell(), Mongo.prototype.runCommand(), and
Mongo.prototype.runCommandWithMetadata().
Also removes a number of tests that were incorrectly blacklisted from
the read_concern_majority_passthrough.yml and
read_concern_linearizable_passthrough.yml test suites.
(cherry picked from commit 35b5b72146ca570b5c6fed8aaa7e891edf7d6a78)
(cherry picked from commit e828226f4c5ab12835e10a09f104759e8fbf09f3)
|
|
|
|
|
|
| |
tracking
(cherry picked from commit 731a5ed5e2859ecc76b1b241c086406f9e6c3867)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Consolidates the logic in the run_check_repl_dbhash.js and
run_validate_collections.js for discovering all of the mongod processes
in a MongoDB deployment into a new discover_topology.js library.
Also adds a test that relies on mongod logging to verify that the
run_check_repl_dbhash.js and run_validate_collections.js hooks execute
on all of the expected servers.
(cherry picked from commit 64bed8173387fbafcfcf39bfb9aa6cecadf25822)
|
|
|
|
|
|
| |
And run ValidateCollections hook on priority=0 secondaries.
(cherry picked from commit b9decc492c0ff942d5bcd6e8c799de70fa0839af)
|
|
|
|
|
|
|
| |
Also fixes the FSM client by changing the concurrency suite to handle
when TestData isn't defined.
(cherry picked from commit fdc23cf6a586a607299ec8a880574e95071e8f39)
|
|
|
|
|
|
| |
CollectionCloner::_verifyCollectionDropped()
(cherry picked from commit 785f56934fcb09f121980ccf6c51d97c3af80fa2)
|
|
|
|
|
|
| |
_verifyCollectionDropped destruction
(cherry picked from commit 73f0e0047afb1f0c0965e4c5e540decdf92c9a72)
|
|
|
|
|
|
| |
while copying documents
(cherry picked from commit b3e32fea3fb27391fce4b170b4dcec1f25b780e4)
|
|
|
|
|
|
| |
resending command
(cherry picked from commit acf7bec77edde339ed6fb1bb89f7f03888144476)
|
| |
|
|
|
|
|
|
|
|
| |
DNS Queries can return superfluous records of non-requested type in
Windows DNSApi calls. Windows implementations will now ignore
records of those types.
(cherry picked from commit bf33c24ff0cf4018dfa94e3a349421ace28d1fac)
|
|
|
|
|
|
| |
restarted once completed
(cherry picked from commit 35b9b4287581fdc9f37d3afeebfb2c9895b2428b)
|
|
|
|
|
|
| |
completion
(cherry picked from commit a046f953101dc64af42da2c72e79a11098f76a7e)
|
|
|
|
|
|
| |
RemoteCommandRetryScheduler::_remoteCommandCallback()
(cherry picked from commit 8b44a736464e31e2a38e40171cb34063f180171c)
|
|
|
|
|
|
| |
increasing _ids.
(cherry picked from commit 0f2cc83cdb0320563f6de507885e9c7b17313fa7)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The batches created by the LogicalSessionCache can exceed the 16mb bson
size limit for bson on the wire. This will cause the refresh step to
fail, preventing logical sessions from ever being synced to the global
collection.
This happens because we don't explicitly size our batches (we were
relying on the write_cmd item batch limit, rather than a byte limit).
Previously the write_cmd batch limit had been 1000 items, which allowed
for 16k per record. The new limit is 100k, which gives a 160 byte
budget we can exceed with very large user names (as we sync the lsid
+ the user@db name).
By forcing a new 10k limit on username sizes used with logical sessions
we can then ensure that a lower 1k limit will always be safe.
(cherry picked from commit 4ae174dd53adaea999715ffbe19c435d685bc412)
|
|
|
|
| |
(cherry picked from commit 260e724de1e8dd8970099b7c3b8d5e00d3edd9a4)
|
|
|
|
|
|
|
|
|
|
| |
dbrefs in the shell can see silent casts from int -> float due to a lack
of special case logic that regular bson objects receive.
For a fix, hook up the special lookup routines in js bsoninfo type into
the js dbrefinfo types.
(cherry picked from commit edebe4d632290b991c291d5e0e0d8bb7e3f0428b)
|
|
|
|
| |
(cherry picked from commit 2f1773ed1edb357ff77144481803a9e6df9481de)
|
|
|
|
| |
(cherry picked from commit 48a34a495386b7cbe18419313768929d12028125)
|
|
|
|
| |
(cherry picked from commit 80186a53de19bc770835096956b4d41d6c99a347)
|
| |
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 5bd4de924cf2da6b50a2bbe073eba22c9f2757fb)
|
|
|
|
| |
replicated sharded cluster
|
|
|
|
| |
(cherry picked from commit ce5691d634b9228b0686e6241e071f6691e46a3f)
|
|
|
|
|
|
|
|
| |
sharded queries.
The deadline has been been already separated for non-sharded queries.
(cherry picked from commit 15a7ac9ca54f2d580e2b1d1ab01fe095be1233db)
|
| |
|