-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
The Shard Role API is intended to be the sole logic that drives yielding and restoring of all resources associated with the Catalog/RSS combo (i.e., locks, storage snapshots, collection catalog and DSS/CSS).
Currently some subset of this logic is duplicated in the APIs used by getMore/releaseMemory.
This ticket is to rewrite this logic to be based on the Shard Role API.