Switch the getMore/releaseMemory logic to use the Shard Role API

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • 3
    • None
    • 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.

            Assignee:
            Unassigned
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: