diff options
| author | Cheahuychou Mao <mao.cheahuychou@gmail.com> | 2020-10-29 22:16:23 +0000 |
|---|---|---|
| committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2020-10-30 15:24:17 +0000 |
| commit | a3a9371325b52e1b86b9491a17c11cef9d4310e9 (patch) | |
| tree | fe3dd777f80d92e6f6effddf02afee17bb9c5d53 | |
| parent | 525bb949dae7a196dbebd767ff79e30b458585f7 (diff) | |
| download | mongo-a3a9371325b52e1b86b9491a17c11cef9d4310e9.tar.gz | |
SERVER-51885 Blacklist balancing_sessions_collection.js from sharding_csrs_continuous_config_stepdown
(cherry picked from commit 49acf2a241db4ed8787fa0f516ff32cc7b51dc66)
| -rw-r--r-- | buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml b/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml index ae5cf3c375b..d730bbdb424 100644 --- a/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml +++ b/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml @@ -157,6 +157,12 @@ selector: - jstests/sharding/regex_targeting.js # Test does not expect the primary config server node to step down. - jstests/sharding/shard_collection_sets_shard_version_on_retry.js + # This test runs removeShard repeatedly until the state is completed. Config server failover could + # cause each _configsvrRemoveShard command after the first one to fail the term number validation + # prior to waiting for write concern. The reason is that the command will not do any write so the + # term in the client opTime could be lower than the actual term. In v4.2 and after, this issue was + # fixed by SERVER-33727. + - jstests/sharding/balancing_sessions_collection.js executor: config: |