diff options
| author | Charlie Swanson <charlie.swanson@mongodb.com> | 2019-02-05 11:43:52 -0500 |
|---|---|---|
| committer | Charlie Swanson <charlie.swanson@mongodb.com> | 2019-02-11 12:13:38 -0500 |
| commit | d568e329a67eee8ba241d52067750a3d8c42dc0f (patch) | |
| tree | e8180ccc44f243f603cb91eaed431afeeabe8676 /buildscripts/resmokeconfig/suites/replica_sets_multi_stmt_txn_kill_primary_jscore_passthrough.yml | |
| parent | b54d9905a167867a2655910799573378aff2ce89 (diff) | |
| download | mongo-d568e329a67eee8ba241d52067750a3d8c42dc0f.tar.gz | |
SERVER-37283 Use stronger locks for system.views
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.
Diffstat (limited to 'buildscripts/resmokeconfig/suites/replica_sets_multi_stmt_txn_kill_primary_jscore_passthrough.yml')
| -rw-r--r-- | buildscripts/resmokeconfig/suites/replica_sets_multi_stmt_txn_kill_primary_jscore_passthrough.yml | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/buildscripts/resmokeconfig/suites/replica_sets_multi_stmt_txn_kill_primary_jscore_passthrough.yml b/buildscripts/resmokeconfig/suites/replica_sets_multi_stmt_txn_kill_primary_jscore_passthrough.yml index e018a67aa39..c5e9e3495e1 100644 --- a/buildscripts/resmokeconfig/suites/replica_sets_multi_stmt_txn_kill_primary_jscore_passthrough.yml +++ b/buildscripts/resmokeconfig/suites/replica_sets_multi_stmt_txn_kill_primary_jscore_passthrough.yml @@ -78,6 +78,9 @@ selector: # Windows debug builds than other builds. - jstests/core/insert1.js + # Reads from system.views. + - jstests/core/views/views_drop.js + ## ## Some aggregation stages don't support snapshot readconcern. ## |