diff options
| author | Justin Seyster <justin.seyster@mongodb.com> | 2019-04-26 20:41:28 -0400 |
|---|---|---|
| committer | Bernard Gorman <bernard.gorman@gmail.com> | 2019-07-26 13:45:35 +0100 |
| commit | 1163d6594381a07cd95a16142166d0c326447360 (patch) | |
| tree | 5a51021e2da8c13d432110e7538ea6f6ab5a6516 | |
| parent | 1cfa8b2ad24612dbf958eb19103652bec8ecc679 (diff) | |
| download | mongo-1163d6594381a07cd95a16142166d0c326447360.tar.gz | |
SERVER-40899 Nix chaining in change_stream_update_lookup_read_concern
(cherry picked from commit a420f5c73bef41aa804a390997897c059afa3713)
| -rw-r--r-- | jstests/sharding/change_stream_update_lookup_read_concern.js | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/jstests/sharding/change_stream_update_lookup_read_concern.js b/jstests/sharding/change_stream_update_lookup_read_concern.js index 183f8b6a860..80f033e8a75 100644 --- a/jstests/sharding/change_stream_update_lookup_read_concern.js +++ b/jstests/sharding/change_stream_update_lookup_read_concern.js @@ -26,6 +26,12 @@ shardsvr: "", }; const replSetName = jsTestName(); + + // Note that we include {chainingAllowed: false} in the replica set settings, because this test + // assumes that both secondaries sync from the primary. Without this setting, the + // TopologyCoordinator would sometimes chain one of the secondaries off the other. The test + // later disables replication on one secondary, but with chaining, that would effectively + // disable replication on both secondaries, deadlocking the test. const rst = new ReplSetTest({ name: replSetName, nodes: [ @@ -34,6 +40,7 @@ {rsConfig: {priority: 0, tags: {tag: "fartherSecondary"}}} ], nodeOptions: rsNodeOptions, + settings: {chainingAllowed: false}, }); if (!startSetIfSupportsReadMajority(rst)) { |