-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
🟥 DDL
-
None
-
None
-
None
-
None
-
None
-
None
Currently, we rely on concrete coordinator implementations to perform causality barriers at the proper points in time.
Consider if the base RecoverableShardingDDLCoordinator/ConfigsvrCoordinator implementations have enough information to do this at the proper times automatically.
See also this comment for more context.
- depends on
-
SERVER-121797 Consider if ParticipantCausalityBarrier can be removed
-
- Backlog
-