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

SERVER-122485 Revert "Enable feature flag for SPM-3729" (Shards persist database metadata authoritatively) (#50294)

Browse Source 
GitOrigin-RevId: a9d96c61b967c79c0696795772de9feb019fd7ca
This commit is contained in:
Pol Piñol Castuera 2026-03-25 18:09:06 +01:00 committed by MongoDB Bot
parent e653a2f9a8
commit 711b8cf20d
7 changed files with 14 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
jstests/multiVersion/genericSetFCVUsage/authoritative_database_metadata_on_FCV_transition.js
View File

@ -5,7 +5,8 @@
* TODO (SERVER-98118): Remove this test.
*
* @tags: [
* requires_fcv_83,
* featureFlagShardAuthoritativeDbMetadataCRUD,
* featureFlagShardAuthoritativeDbMetadataDDL,
* ]
*/
import {FeatureFlagUtil} from "jstests/libs/feature_flag_util.js";

3
jstests/noPassthrough/global_catalog/authoritative_db_metadata_vs_ddls.js
View File

@ -4,7 +4,8 @@
* collection.
*
* @tags: [
* requires_fcv_83,
* featureFlagShardAuthoritativeDbMetadataCRUD,
* featureFlagShardAuthoritativeDbMetadataDDL,
* ]
*/

3
jstests/noPassthrough/global_catalog/clone_authoritative_db_metadata.js
View File

@ -8,7 +8,8 @@
* upgrade procedure.
*
* @tags: [
* requires_fcv_83,
* featureFlagShardAuthoritativeDbMetadataCRUD,
* featureFlagShardAuthoritativeDbMetadataDDL,
* ]
*/

3
jstests/noPassthrough/local_catalog/authoritative_db_metadata_restore_playbook.js
View File

@ -5,7 +5,8 @@
* because the restarted node relies on the replica set config persisted to disk to know that it
* is initialized as part of a replica set and should run for election.
* @tags: [
* requires_fcv_83,
* featureFlagShardAuthoritativeDbMetadataCRUD,
* featureFlagShardAuthoritativeDbMetadataDDL,
* requires_persistence,
* ]
*/

3
jstests/noPassthrough/local_catalog/get_database_version.js
View File

@ -2,7 +2,8 @@
* Test getDatabaseVersion command after the effects of database DDLs.
*
* @tags: [
* requires_fcv_83,
* featureFlagShardAuthoritativeDbMetadataCRUD,
* featureFlagShardAuthoritativeDbMetadataDDL,
* ]
*/

3
jstests/noPassthrough/sharded_cluster_topology/promotion_to_sharded_authoritative.js
View File

@ -3,7 +3,8 @@
* # This test is incompatible with 'config shard' as it creates a cluster with 0 shards in order
* # to be able to add shard with data on it (which is only allowed on the first shard).
* config_shard_incompatible,
* requires_fcv_83,
* featureFlagShardAuthoritativeDbMetadataDDL,
* featureFlagShardAuthoritativeDbMetadataCRUD,
* # This test restarts the server and requires that data persists across restarts.
* requires_persistence,
* ]

6
src/mongo/db/sharding_environment/sharding_feature_flags.idl
View File

@ -135,8 +135,7 @@ feature_flags:
"Feature flag to enable the authoritative model to read database metadata from
stored shard-local information"
cpp_varname: feature_flags::gShardAuthoritativeDbMetadataCRUD
default: true
version: 8.3
default: false
fcv_gated: true
# TODO (SERVER-98118): remove once 9.0 becomes last LTS.
featureFlagShardAuthoritativeDbMetadataDDL:
@ -150,8 +149,7 @@ feature_flags:
If this feature flag is disabled by a FCV downgrade, all DDL coordinators checking
this flag are drained when finalizing the downgrade.
cpp_varname: feature_flags::gShardAuthoritativeDbMetadataDDL
default: true
version: 8.3
default: false
fcv_gated: true
enable_on_transitional_fcv_UNSAFE: true
# TODO (SERVER-89169): remove once 9.0 becomes last LTS.