-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In order to detect whether the CSS is currently shard authoritative or not we will use the critical section release step to determine it as we did for authoritative databases.
To do this we expect the critical section release to perform the following depending on whether the originating DDL is authoritative or not:
- In the event of a non-authoritative DDL we clear the filtering metadata (already done today) and flag the CSS as non-authoritative
- In the event of an authoritative DDL we don't clear the filtering metadata and the CSS is flagged as authoritative
- depends on
-
SERVER-119832 Modify CSS to contain information on whether it is authoritative or not
-
- Closed
-
- is depended on by
-
SERVER-119844 Drop all contents of the authoritative shard collections for a namespace when doing a non-authoritative DDL
-
- Backlog
-
-
SERVER-119837 Modify _shardSvrFetchCollMetadata to not clone data if the CSS is already authoritative
-
- Backlog
-