Better handling for running out of WT sessions

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There is a (configurable) fixed number of WT sessions available both for the main WT instance and for the spill WT instance. If an operation tries to get a session when there are no more available, we should handle this gracefully as opposed to just failing the operation.

            Assignee:
            Unassigned
            Reporter:
            Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: