mongodb/mongo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

SERVER-127321: Remove explicit featureFlagReshardingVerification setting in resharding test (#54280)

Browse Source 
Co-authored-by: mongodb-sage-bot[bot] <247496174+mongodb-sage-bot[bot]@users.noreply.github.com>
Co-authored-by: Kruti Shah <kruti139@gmail.com>
GitOrigin-RevId: ae881b4792366c073e915637f3dc322d613e954c
This commit is contained in:
mongodb-sage-bot[bot] 2026-05-26 16:46:45 +00:00 committed by MongoDB Bot
parent 1bc91fd5d7
commit 1722ac245f
1 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
jstests/sharding/resharding_with_write_concern_timeout.js
View File

@ -3,7 +3,8 @@
*
* @tags: [
* requires_sharding,
* requires_fcv_83
* requires_fcv_83,
* resource_intensive,
* ]
*/
import {configureFailPoint} from "jstests/libs/fail_point_util.js";
@ -160,14 +161,9 @@ function testWriteConcernFailover(st) {
}
function runTests() {
// TODO Do not explicitly set this feature flag after SERVER-109032 is done.
const featureFlagReshardingVerification = false;
const st = new ShardingTest({
shards: 3,
rs: {nodes: 3, setParameter: {featureFlagReshardingVerification}},
other: {
configOptions: {setParameter: {featureFlagReshardingVerification}},
},
rs: {nodes: 3},
});
testWriteConcernBasic(st);
testWriteConcernFailover(st);