-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
CAR Team 2026-03-16
-
None
-
None
-
None
-
None
-
None
-
None
-
None
DDL locks are currently used to serialize DDLs on the same namespace on sharded clusters.
Considering that on replica sets there are some DDLs such as collMod that acquire/release/re-acquire the collection lock during their execution, it would be useful to use the DDL locks also on replica sets.
Benefits:
- Prevent concurrent DDLs from sneaking in
- Check preconditions before acquiring db/collection locks in strong modes in order to avoid unnecessary lock contention and have the guarantee that preconditions will hold during the whole duration of the operation
NB: if some DDL at replica set level is not atomic, this would still not prevent DDLs from getting half-committed upon stepdown/crash.
- derives
-
-
- Closed
-
- is depended on by
-
SERVER-90862 Creating a collection or a view should fail if a bucket namespace exists without its view
-
- Blocked
-
-
-
- Blocked
-
-
-
- Blocked
-
-
SERVER-95760 $out: acquire locks for target namespaces when outputting to timeseries
-
- Blocked
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- In Code Review
-