Allocate individual thread pools per resharding operation

ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • 9.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ClusterScalability 26Oct-9Nov
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Concurrent reshardings on distinct namespaces (see SERVER-136621) currently share a single PrimaryOnlyService thread pool per service. The coordinator admission cap max(1, (reshardingCoordinatorServiceMaxThreadCount - 1) / 3) exists only to keep concurrent operations from starving each other on that shared pool. Give each resharding operation its own thread pool, so concurrency scales until machine resources are the limit. the follow up work will remove the cap's dependency on MaxThreadCount and revert the MaxThreadCount server parameter values to their original defaults (SERVER-138643), but this ticket should not do that.

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

              Created:
              Updated: