[SERVER-53776]  Create feature flag to guard incomplete DDL operations Created: 14/Jan/21  Updated: 20/Jan/21  Resolved: 20/Jan/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Duplicate Votes: 0
Labels: PM-1965-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-53772 Create feature flag for timestamp bas... Closed
Related
related to SERVER-52809 Implement the new drop collection pat... Closed
Participants:

 Description   

Until PM-1965-Milestone-1 will be completed, the new DDL operations implementations won't be resilient to shutdown/stepdown and concurrent workloads. So we need to introduced a new feature flag that will prevent the concurrency and step-down suites to run incompleted DDL operations.

The idea is that we will have two feature flags:
 - featureFlagShardingDDLSupport - featureFlagDisableIncompleteShardingDDLSupport

 

ShardingDDLSupport flag will be enable for all the "all feature flags" variants, while the DisableIncompleteShardingDDLSupport flag will be enable in all the shutdown/stepdown suites.

The new DDL operation's paths will be executed in the code only if:
(featureFlagShardingDDLSupport && !featureFlagDisableIncompleteShardingDDLSupport)

So probably we need also to introduce a wrapper to hide this complexity around the featureFlag/FCV check.



 Comments   
Comment by Tommaso Tocci [ 20/Jan/21 ]

The new flag has been added as part of SERVER-52809

Generated at Thu Feb 08 05:31:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.