Remove resharding op cap dependency on thread pool max counts and reset thread pool to original defaults

ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After SERVER-138049 lands, the maximum number of resharding operations that can run concurrently will no longer depend on/be a function of the server parameters for maximum thread pool count for coordinator/donors/recipients. We should change the logic so that it no longer depends on those values, and we should also reset those values back to their defaults (coordinator = 5, donor = 2, recipient = 8).

      The cap can be some hard coded value for now. Afterwards, SERVER-138298 can make it a cluster parameter.

            Assignee:
            Anja Kalaba
            Reporter:
            Anja Kalaba
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: