summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPol Pinol Castuera <pol.pinol@mongodb.com>2023-05-05 11:40:10 +0000
committerEvergreen Agent <no-reply@evergreen.mongodb.com>2023-05-05 12:24:06 +0000
commitd9cefb0cfe083fba895c79cf797ddd674961a1ef (patch)
tree1f86b72acc07b4d8f1d2727a2c00df06012850f9
parente4866d1dddd165076a4a6ced76d9b8e6d37601fc (diff)
downloadmongo-d9cefb0cfe083fba895c79cf797ddd674961a1ef.tar.gz
SERVER-40172 Unblacklist merge_to_existing from sharding_csrs_continuous_config_stepdown
-rw-r--r--buildscripts/resmokeconfig/suites/sharding_csrs_continuous_config_stepdown.yml5
1 files changed, 0 insertions, 5 deletions
diff --git a/buildscripts/resmokeconfig/suites/sharding_csrs_continuous_config_stepdown.yml b/buildscripts/resmokeconfig/suites/sharding_csrs_continuous_config_stepdown.yml
index b0c9b024339..7791d693acb 100644
--- a/buildscripts/resmokeconfig/suites/sharding_csrs_continuous_config_stepdown.yml
+++ b/buildscripts/resmokeconfig/suites/sharding_csrs_continuous_config_stepdown.yml
@@ -192,11 +192,6 @@ selector:
- jstests/sharding/merge_requires_unique_index.js
- jstests/sharding/query/merge_stale_on_fields.js
- jstests/sharding/query/out_fails_to_replace_sharded_collection.js
- # In this suite the cluster may end up in a state where each shard believes the
- # collection is sharded and the mongos believes it is unsharded. $merge is not
- # prepared to work correctly in this situation. This should be fixed by a future
- # improvement in sharding infrastructure, and can be undenylisted by SERVER-40172.
- - jstests/sharding/query/merge_to_existing.js
# Sets a failpoint on find commands which can lead to a hang when a config steps down.
- jstests/sharding/sharding_statistics_server_status.js
# setShardVersion is not robust during config server stepdown.